bug#31990: 26.1; Stuck in loop trying to send bug report

[Live System User <nyc4bos@aol.com>]

Robert Pluim <rpluim@gmail.com> writes:

> Live System User <nyc4bos@aol.com> writes:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>>>> From: Live System User <nyc4bos@aol.com>
>>>> Cc: 31990@debbugs.gnu.org
>>>> Date: Fri, 10 Aug 2018 04:53:16 -0400
>>>> 
>>>> >>   It was done manually anew in each session, yes.
>>>> >
>>>> > Then you should be able to manually set the variables derived from the
>>>> > auth file, no?
>>>> 
>>>>   Unfortunately, no, as there is only the variable `smtpmail-smtp-user'
>>>>   and no "smtpmail-smtp-password"-like variable...
>>>
>>> Then perhaps we should add them.
>
> And then people go 'but I want different values for different
> accounts', and weʼre back at the .authinfo solution.
>
>>   Yes, although I would prefer that the solution would be more
>>   comprehensive and allow users to make first-time *authenicated*
>>   connections instead of retrying (with a subsequent prompt for
>>   the password) only after a first-time *unauthenicated* connection
>>   failure.
>>
>>   This would better solve this issue and for bug#26359 as well.
>>
>>> I do consider yours a very strange use case, btw.
>>
>>   I do it for my sense of privacy (as little as it may be).
>
> Adding just the smtp username into .authinfo is really that much of an
> issue for you?

  I don't want that information for 2 accounts *stored on disk*.

>                Given that youʼre using initially-unencrypted SMTP
> connections,

  This issue is *also* present in an initially-*ENCRYPTED* TlS SMTP
  connection (port 465).

>              I fail to see the benefit to your privacy.

  Would you use similiar arguments for those who chose NOT to store
  their SMTP pasword in an (encrypted) .authinfo file?

>>   To each's own...
>
> Indeed.

  Then, nopefully, this option will be restored back in Emacs.

  Thanks.

>
> Robert