From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: [nnimap gmail] confused by phenomena
Date: Thu, 23 May 2013 16:49:29 -0400 [thread overview]
Message-ID: <87ehcxv2ue.fsf@newsguy.com> (raw)
In-Reply-To: <87ehcxonp4.fsf@topper.koldfront.dk>
asjo@koldfront.dk (Adam Sjøgren) writes:
> Harry Putnam <reader@newsguy.com> writes:
>
>> (add-to-list 'gnus-secondary-select-methods '(nnimap "hputnam3"
>> (nnimap-address "imap.gmail.com")))
>>
>> <this one was added yesterday>
>> (add-to-list 'gnus-secondary-select-methods
>> '(nnimap "harrygp3"
>> (nnimap-address "imap.gmail.com")))
>
> How is Gnus going to find the relevant .authinfo-line for those select
> methods?
>
> The only thing that differs is the name, and how would Gnus know to
> partially match that with the "login" field in the .authinfo file?
>
>> machine imap.gmail.com login hputnam3@gmail.com password xxxxxxxx port imap
>> machine imap.gmail.com login harrygp3@gmail.com password xxxxxxxx port imap
>
> The manual should be more explicit about how this is handled, I think.
[...]
Well, I did say that I was confused... and can only re-emphasize that.
I guess I don't understand your reasoning here. Is it not possible
for gnus to find the correct line by the uid? Nothing partial
involved but an exact match on uid (LOGNAME).
Its obvious I don't have a clue how this actually works... but I would
have thought that as all things in unix/linux if you want to access
the correct account you need and host and login name, right? Where
does the 'partial' matching you refer to, come in?
next prev parent reply other threads:[~2013-05-23 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 10:58 Harry Putnam
2013-05-22 11:09 ` Alberto Luaces
2013-05-22 11:39 ` Harry Putnam
2013-05-23 13:00 ` Adam Sjøgren
2013-05-23 20:49 ` Harry Putnam [this message]
2013-05-23 22:11 ` Adam Sjøgren
2013-05-25 21:51 ` Harry Putnam
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=87ehcxv2ue.fsf@newsguy.com \
--to=reader@newsguy.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).