From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: emacs-devel@gnu.org
Subject: Re: Outgoing mail defaults
Date: Thu, 17 Mar 2011 13:18:54 -0500 [thread overview]
Message-ID: <87r5a5390x.fsf@lifelogs.com> (raw)
In-Reply-To: <m3aagty7ox.fsf@quimbies.gnus.org>
On Thu, 17 Mar 2011 18:31:58 +0100 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> Ted Zlatanov <tzz@lifelogs.com> writes:
>> smtpmail can get auth-source to do 1+2 better that Customize IMO through
>> `auth-source-creation-prompts' and `auth-source-creation-defaults'.
LMI> Hm... but we still have to set what the smtp host is somewhere? Or
LMI> were you thinking that smtpmail could just ask auth-source for "give me
LMI> an smtp host from your backends", which would, for most people, be a
LMI> line from their ~/.authinfo file saying
LMI> machine smtp.gmail.com port smtp
Right, it would be the first SMTP host found or none if they don't have
one. I think that's the right thing either way for most new cases.
>> Perhaps auth-source itself should be smarter when running for the first
>> time, asking the user if he'd like to use the Secrets API, or (on Mac OS
>> X) the upcoming keychain support, or an unencrypted file on Windows, or
>> some other auth-source backend. The default works for those who use
>> EPA/EPG and cache or agentize their passphrases, but otherwise it's
>> annoying.
LMI> Yeah, auth-source could be querying the user about this stuff the first
LMI> time it runs. (And it could determine whether it's the first time just
LMI> by trying all the sources, and see whether any of them exist?)
Hmm, what a pain. Yes, it makes sense to build the auth-sources more
intelligently. It shouldn't stop the smtpmail.el changes you're
planning. I'll put it on my TODO list.
Ted
next prev parent reply other threads:[~2011-03-17 18:18 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 17:04 Lars Magne Ingebrigtsen
2011-03-17 17:17 ` Ted Zlatanov
2011-03-17 17:31 ` Lars Magne Ingebrigtsen
2011-03-17 18:18 ` Ted Zlatanov [this message]
2011-03-17 18:33 ` Lars Magne Ingebrigtsen
2011-03-17 19:35 ` Ted Zlatanov
2011-03-17 17:25 ` David Reitter
2011-03-17 17:43 ` Lars Magne Ingebrigtsen
2011-03-17 18:22 ` Ted Zlatanov
2011-03-18 14:10 ` John Sullivan
2011-03-17 19:02 ` David Reitter
2011-03-17 22:27 ` chad
2011-03-18 2:38 ` Ted Zlatanov
2011-03-18 4:17 ` chad
2011-03-21 19:46 ` Adam Sjøgren
2011-03-21 19:50 ` Ted Zlatanov
2011-03-17 20:23 ` James Cloos
2011-03-17 20:30 ` Lars Magne Ingebrigtsen
2011-03-17 20:35 ` James Cloos
[not found] ` <87d3ln9b7y.fsf@stupidchicken.com>
2011-03-20 1:41 ` Ted Zlatanov
2011-03-20 3:06 ` Stefan Monnier
2011-03-20 12:20 ` Ted Zlatanov
2011-03-21 14:20 ` Stefan Monnier
2011-03-21 19:42 ` Ted Zlatanov
2011-03-21 22:14 ` Stefan Monnier
2011-03-22 2:01 ` Ted Zlatanov
2011-03-29 19:22 ` Lars Magne Ingebrigtsen
2011-03-29 19:34 ` Application resource storage (was: Outgoing mail defaults) Lars Magne Ingebrigtsen
2011-03-29 19:58 ` Application resource storage Ted Zlatanov
2011-03-29 20:14 ` Lars Magne Ingebrigtsen
2011-03-29 21:02 ` Ted Zlatanov
2011-03-29 20:51 ` chad
2011-03-22 11:26 ` Outgoing mail defaults Simon Josefsson
2011-04-16 16:45 ` Lars Magne Ingebrigtsen
2011-04-16 16:47 ` Lars Magne Ingebrigtsen
2011-04-16 16:51 ` Ted Zlatanov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r5a5390x.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@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.
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 NNTP newsgroup(s).