From: Paul Rankin <paul@tilk.co>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Mac OS Keychain with SMTP
Date: Wed, 26 Nov 2014 15:56:26 +1000 [thread overview]
Message-ID: <m2egsqsdx1.fsf@tilk.co> (raw)
In-Reply-To: <87ppcb4n65.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Tue, 25 Nov 2014 15:15:15 +1000 Paul Rankin <paul@tilk.co> wrote:
>
> PR> I'd like to eschew an .authinfo file in favour of the Mac OS Keychain
> PR> but can't seem to get it going. I keep receiving the error:
>
> PR> auth-source-macos-keychain-search: The MacOS Keychain auth-source
> PR> backend doesn't support creation yet
>
> Please see Emacs bug#19074: Bug in auth-source.el's search of OS X
> Keychain at https://lists.gnu.org/archive/html/bug-gnu-emacs/2014-11/msg00805.html
>
> There's a patch there which I haven't been able to test. If you could,
> please try it and let me know your experience (in the bug thread or
> here). You will have to pre-create your security tokens in the Mac
> OS X, since creating them through auth-source.el is not supported yet.
I applied the patch and can now successfully use SMTP with a password
without an .authinfo file.
One further problem I had was that `auth-source.el` seems to always
query `security` with a port number, and I hadn't added a port number to
the keychain item in question, so, in Keychain Access.app
Where: smtp://mail.example.com:465
fixed the problem.
This is probably a silly question, but if I don't want to mess with my
Emacs distribution, I should just put the patched version of
`auth-source-macos-keychain-search-items` into my init file right?
--
Paul W. Rankin
http://www.paulwrankin.com
Before printing this email please take a moment to think about the
environment. Just stop and think about it. Think about the last time you
were walking alone in a forest, how you felt at peace, how a wave of
clarity seemed to overcome you and you had to stop and reevaluate your
life, what you're doing with the limited time you have here. "Damn," you
thought, "life is so precious. I should really be doing ______." Are you
doing that now? Why not? Go on, pick up your computer and throw it out
the window! It'll be great, like that scene from Network where everyone
starts yelling "I'M MAD AS HELL AND I'M NOT GOING TO TAKE THIS ANY
MORE." That'll be you, but it will be real. Now's your moment.
next prev parent reply other threads:[~2014-11-26 5:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.14515.1416892539.1147.help-gnu-emacs@gnu.org>
2014-11-25 9:58 ` Mac OS Keychain with SMTP Ted Zlatanov
2014-11-26 5:56 ` Paul Rankin [this message]
[not found] ` <mailman.14638.1416984364.1147.help-gnu-emacs@gnu.org>
2014-11-26 14:08 ` Ted Zlatanov
2014-11-28 3:45 ` Paul Rankin
2014-11-28 4:13 ` Paul Rankin
2014-11-25 5:15 Paul Rankin
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=m2egsqsdx1.fsf@tilk.co \
--to=paul@tilk.co \
--cc=help-gnu-emacs@gnu.org \
--cc=tzz@lifelogs.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.
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).