GNU bug report logs - #31990
26.1; Stuck in loop trying to send bug report

Previous Next

Package: emacs;

Reported by: Live System User <nyc4bos <at> aol.com>

Date: Wed, 27 Jun 2018 23:56:02 UTC

Severity: normal

Tags: fixed

Merged with 26359, 35682

Found in versions 25.2, 26.1, 27.0.50

Fixed in version 27.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Robert Pluim <rpluim <at> gmail.com>
To: Live System User <nyc4bos <at> aol.com>
Cc: 31990 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#31990: 26.1; Stuck in loop trying to send bug report
Date: Tue, 21 Aug 2018 12:22:19 +0200
Live System User <nyc4bos <at> aol.com> writes:

> Robert Pluim <rpluim <at> gmail.com> writes:
>
>> Live System User <nyc4bos <at> aol.com> writes:
>>
>>>> Then how do you expect emacs to know that for those 2 particular
>>>> servers it should prompt straight away?
>>>
>>>   Because (I believe) that the protocol requires a "password" or
>>>   certificate.
>>
>> Thatʼs unfortunately not the way SMTP authentication works,
>
>   I thought from my original message that you responded to that
>   you understood that the "protocol" I'm referring to (above) is
>   TLS (in conjunction with SMTP), not SMTP separately or in the
>   absense of a TLS connection.
>
>   Perhaps we are miscommunicating?

We are. Iʼm only talking about SMTP authentication, not TLS. Without
going back and rereading, my memory says that it turned out you were
not having a TLS issue.

>
>>                        itʼs very
>> much optional
>
>   I believe that either a "password" or a certicate is needed
>   to establish a TLS conection and not optional.
>

You need a certificate on the server side for TLS. For SMTP auth you
need a password. The two are completely separate protocols.

>>               (and some servers change their authentication
>> requirements based on the recipient of the mail youʼre trying to
>> send).
>
>   Are we still talking about TLS connectons?
>   
>   Unless there is NO authenication required, a changed authenication
>   requirement is still an authenication requiring a "password" or
>   certificate if it involves TLS, nonetheless.
>
>   That valid "password" can even be blank, an email address or anything
>   (including the recipient) depending on the server's valid authenication
>   method.
>
>   I'm saying that I believe the SSL/TLS or STARTTLS protocols require
>   a "password" or certficate.  Are you saying that's incorrect or it's
>   not necessarily so?
>>

As noted above, Iʼm only talking about SMTP authentication.

Robert




This bug report was last modified 5 years and 295 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.