unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Live System User <nyc4bos@aol.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31990@debbugs.gnu.org
Subject: bug#31990: 26.1; Stuck in loop trying to send bug report
Date: Mon, 20 Aug 2018 23:56:18 -0400	[thread overview]
Message-ID: <87zhxg8ja5.fsf@aol.com> (raw)
In-Reply-To: <87sh39e5ao.fsf@gmail.com> (Robert Pluim's message of "Mon, 20 Aug 2018 11:49:35 +0200")

Robert Pluim <rpluim@gmail.com> writes:

> Live System User <nyc4bos@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?

>                        itʼs very
> much optional

  I believe that either a "password" or a certicate is needed
  to establish a TLS conection and not optional.

>               (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?
>
>>
>>>                                         Or are you asking for a
>>> generic 'if AUTH in capabilities then prompt username and password'
>>> feature?
>>
>>   I'm requesting to restore the capability that
>>   `smtpmail-auth-credentials' provided previously.
>>
>>>
>>>>   Previously, one used `smtpmail-auth-credentials' for this.
>>>
>>> Which as Eli points out needed to be stored somewhere as well.
>>
>>   But it doesn't have to be stored on *disk*.
>>
>>   It can be defined anew each Emacs session and thus only "stored"
>>   in *memory*.
>
> I would find it very annoying to have to do that, but to each his
> own. I doubt that having the username in memory is any more secure
> than having it in an encrypted file.

  I'm sure that there are those that feel that same way about passwords.

  And even so they still feel more comfortable not storing their
  passsword, even in an encryped file, on disk.
>
> Having said that, there might be a case that smtpmail should prompt
> for authentication if smtpmail-smtp-user is set even without a
> corresponding .authinfo setting. Iʼll take a look.

  `smtpmail-auth-credentials' use to facilitate this.

  A similiar methodology would suffice.

>                                  Iʼll take a look.

  Thanks.
>
> Robert





  reply	other threads:[~2018-08-21  3:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 22:41 bug#31990: 26.1; Stuck in loop trying to send bug report Live System User
2018-06-28 13:31 ` Eli Zaretskii
2018-06-29 13:32 ` Live System User
2018-06-29 14:55   ` Robert Pluim
2018-07-08  9:41     ` Live System User
2018-07-10 12:11       ` Robert Pluim
2018-07-10 17:25         ` Live System User
2018-07-11  9:19           ` Robert Pluim
2018-07-11 20:47             ` Live System User
2018-07-12  2:33               ` Eli Zaretskii
2018-08-09 21:54                 ` Live System User
2018-08-10  6:09                   ` Eli Zaretskii
2018-08-10  8:53                     ` Live System User
2018-08-10  9:50                       ` Eli Zaretskii
2018-08-10 13:50                         ` Live System User
2018-08-20  9:42                           ` Robert Pluim
2018-08-20 11:21                             ` Noam Postavsky
2018-08-20 23:38                             ` Live System User
2018-07-12  8:04               ` Robert Pluim
2018-08-09 22:18                 ` Live System User
2018-08-20  9:49                   ` Robert Pluim
2018-08-21  3:56                     ` Live System User [this message]
2018-08-21 10:22                       ` Robert Pluim
2018-08-21 16:02                         ` Live System User
2019-07-26 13:12                           ` Robert Pluim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhxg8ja5.fsf@aol.com \
    --to=nyc4bos@aol.com \
    --cc=31990@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).