From: Robert Pluim <rpluim@gmail.com>
To: Live System User <nyc4bos@aol.com>
Cc: 31990@debbugs.gnu.org
Subject: bug#31990: 26.1; Stuck in loop trying to send bug report
Date: Tue, 10 Jul 2018 14:11:19 +0200 [thread overview]
Message-ID: <871scbz3x4.fsf@gmail.com> (raw)
In-Reply-To: <E1fYKGs-0005X3-In@eggs.gnu.org>
Live System User <nyc4bos@aol.com> writes:
> Unfortunately, Emacs only records in its
> *trace of SMTP sesssion to...* buffer the responses from
> the SMTP server and mot also what commands are sent to it.
> So while I presumed that a STARTTLS command wasn't being
> issued because it failed and I wasn't being asked to
> provide a password, a now closer look reveals that it
> apparently was sent.
>
> So it's failing for another reason which a direct TLS
> connection helps to confirm.
>
> It appears I have a similar problem as Ulrich Mueller
> which he reported back April of last year in bug#26359;
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=26359
>
> His workaround. a `defadvice` also works for me.
>
> Hopefully. a fix will solve these issues and allow one to
> designatre for a partiular network connection that a
> password is required (supplied or prompted for) upon an
> initial connection and not just only after an initial
> unauthenticated connetion failure;
>
This is already in place, and it works for me, but itʼs not working
correctly for you. Could you provide more details on how youʼre
specifying your username/password? Based on looking at the code, this
situation could arise if you only set smtpmail-smtp-user without
having an entry in .authinfo.
Thanks
Robert
next prev parent reply other threads:[~2018-07-10 12:11 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 [this message]
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
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=871scbz3x4.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=31990@debbugs.gnu.org \
--cc=nyc4bos@aol.com \
/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).