From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 6216c7a: Allow specifying that SMTP auth should always be used
Date: Fri, 26 Jul 2019 14:47:38 +0200 [thread overview]
Message-ID: <m2ftmtj72t.fsf@gmail.com> (raw)
In-Reply-To: <m34l399eyx.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 26 Jul 2019 14:07:18 +0200")
>>>>> On Fri, 26 Jul 2019 14:07:18 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Larsi> Robert Pluim <rpluim@gmail.com> writes:
>> If the user can customize smtpmail-servers-requiring-authorization,
>> then they can also add an appropriate entry to .authinfo to make
>> smtpmail do authentication, so why is such a variable needed?
Larsi> smtpmail always tries first without auth, and then starts looking around
Larsi> for credentials if the SMTP servers says "give me credentials".
I was convinced thatʼs not how it worked, but the code disagrees with
me.
Larsi> We could make it start sending credentials immediately if there's an
Larsi> .authinfo entry, but that'd be a behaviour change, and the user may have
Larsi> specified just "machine my.mail.host" for (for instance) IMAP usage, and
Larsi> there's no auth on SMTP, in which case the SMTP server may deny the
Larsi> connection.
And again I was convinced we did port matching, but again thatʼs not
how auth-source works when the machine entry doesnʼt have a port.
Larsi> And besides, the user may be typing in the credentials and not using
Larsi> .authinfo.
I appear to be 0 for 3 here. Oh well.
Robert
next prev parent reply other threads:[~2019-07-26 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190726101658.4938.74351@vcs0.savannah.gnu.org>
[not found] ` <20190726101700.307C020C06@vcs0.savannah.gnu.org>
2019-07-26 11:56 ` master 6216c7a: Allow specifying that SMTP auth should always be used Robert Pluim
2019-07-26 12:07 ` Lars Ingebrigtsen
2019-07-26 12:47 ` Robert Pluim [this message]
2019-07-26 14:12 ` Stefan Monnier
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=m2ftmtj72t.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).