From: Ted Zlatanov <tzz@lifelogs.com>
Cc: Ding Mailing List <ding@gnus.org>
Subject: Re: multiple Gmail accounts + nnimap + ~/.authinfo
Date: Wed, 09 Apr 2008 15:20:16 -0500 [thread overview]
Message-ID: <86bq4i7pbz.fsf@lifelogs.com> (raw)
In-Reply-To: <mailman.10210.1207766032.18990.info-gnus-english@gnu.org> (Suno Ano's message of "Wed, 09 Apr 2008 20:30:44 +0200")
The following message is a courtesy copy of an article
that has been posted to gnu.emacs.gnus as well.
On Wed, 09 Apr 2008 20:30:44 +0200 Suno Ano <suno.ano@googlemail.com> wrote:
>> | On Wed, 09 Apr 2008 12:31:30 -0500,
>> | Ted Zlatanov
>> | from the organization of Теодор Златанов @ Cienfuegos
>> | who can be reached at: tzz@lifelogs.com
>> | (whose comments are cited below with " Ted> "),
>> | had this to say in article <86hceb6ikt.fsf@lifelogs.com>
>> | in newsgroups gmane.emacs.gnus.user
>> | concerning the subject of Re: multiple Gmail accounts + nnimap + ~/.authinfo
>> | (see <mailman.10199.1207755910.18990.info-gnus-english@gnu.org> for more details)
Ted> ...Assuming your method is called "gmail1"?
SA> well, it's called "<gmail_1>@gmail.com" but then that should not make a
SA> difference to calling it just "gmail1" - yes?
Right, it was just for the example.
Ted> We could also make 'machine' a more complex field, but I don't
Ted> like that approach.
SA> Why is it you do not like it?
It's harder to parse and write. I usually try to keep files like
~/.authinfo free of Gnus-specific extensions because other systems may
break when they parse it.
Another approach is to have a specific authinfo file for each server. I
don't like that approach much.
Ted> Any opinions?
SA> Well, before I used nnimap I used nnml as back end. With this back end
SA> and the following snippet it worked like charm. Maybe we could try it
SA> this way for nnimap too? What do others think about it?
SA> (add-to-list 'mail-sources `(imap :server ,priv-imap-gmail-mail-server
SA> :user ,priv-gmail1-mail-user
SA> :password ,priv-imap-gmail1-password
SA> :port 993
SA> :stream ssl
SA> :authentication login
SA> )
SA> )
mail-source.el and nnimap.el get authentication info in very different
ways currently. In fact I'm in the process of writing auth-source.el
(it's about 50% finished now) which will unite mail-source.el,
nnimap.el, SMTP, and all the other Gnus authentication hooks into one
sensible structure. You can look at the auth-source.el code to see what I
mean. Currently it doesn't support multiple accounts per server, so
it's good you brought up that use case. I've added the necessary code
to auth-source.el, and will add server support to netrc.el when
we agree on how that should look in ~/.authinfo..
Ted
next parent reply other threads:[~2008-04-09 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.10199.1207755910.18990.info-gnus-english@gnu.org>
[not found] ` <86hceb6ikt.fsf@lifelogs.com>
[not found] ` <mailman.10210.1207766032.18990.info-gnus-english@gnu.org>
2008-04-09 20:20 ` Ted Zlatanov [this message]
2008-04-09 19:13 Suno Ano
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=86bq4i7pbz.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@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.
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).