From: Jun Hao <jun_hao@aol.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 22824@debbugs.gnu.org
Subject: bug#22824: Use smtpmail-smtp-user if auth-source-search doesn't return user field
Date: Sun, 28 Feb 2016 17:07:19 +0800 [thread overview]
Message-ID: <m2io19nqyg.fsf@aol.com> (raw)
In-Reply-To: <87vb59v1r0.fsf@gnus.org>
I'm working on fix auth-source-search. This is actually affecting any
field (including password) with these kind of symbols and non-ASCII chars. Will post a patch
once I'm done.
I think it's safe to assume what auth-source-search returns should match
smtpmail-smtp-user and no harm to fallback to it. But if you think it's
confusing, let's just drop this patch.
It's utf-8 encoded.
On 2016-02-28 at 13:32, Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Jun Hao <jun_hao@aol.com> writes:
>
>> Long term is to fix auth-source-search. Looks like it missed this case
>> in auth-source-macos-keychain-search-items. If account has '\' in it,
>> security will return something like:
>>
>> "acct"<blob>=0x414E545C6A756E68616F "ANT\134junhao"
>>
>> instead of form current code expects:
>>
>> "acct"<blob>="junhao"
>>
>> Even auth-source-search is fixed, I still think this patch is nice
>> to have to make smtpmail more robust.
>
> Well, this is purely a bug in auth-source, so I think a workaround in
> smtpmail.el would just be confusing.
>
> What is that encoding of the user name that the MacOS keychain uses?
next prev parent reply other threads:[~2016-02-28 9:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 7:52 bug#22824: Use smtpmail-smtp-user if auth-source-search doesn't return user field Jun Hao
2016-02-28 5:32 ` Lars Ingebrigtsen
2016-02-28 9:07 ` Jun Hao [this message]
2016-02-29 2:22 ` Lars Ingebrigtsen
[not found] ` <m2si09f19c.fsf@aol.com>
2016-03-02 16:58 ` Lars Ingebrigtsen
[not found] ` <m2k2ljfyuj.fsf@aol.com>
2016-03-03 16:54 ` Lars Ingebrigtsen
2016-03-03 16:59 ` Glenn Morris
[not found] ` <m2mvqegwtu.fsf@aol.com>
[not found] ` <m2bn5d7fjw.fsf@aol.com>
2016-04-24 12:37 ` Lars Magne Ingebrigtsen
2016-04-24 12:43 ` Lars Magne Ingebrigtsen
2016-04-25 14:41 ` Jun Hao
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=m2io19nqyg.fsf@aol.com \
--to=jun_hao@aol.com \
--cc=22824@debbugs.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).