From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: How to setup multiple imap accounts at single server
Date: Sat, 14 Jun 2003 22:29:51 +0200 [thread overview]
Message-ID: <84llw42yio.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <v98ys5hst8.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> On Fri, Jun 13 2003, Kai Großjohann wrote:
>
>> I'm no less amazed, then, that it works for me. I have this:
> [...]
>> Hm. So I'm using the real host name after all.
>
> Maybe we should call `gnus-netrc-machine' first with `server' and, if
> that is nil with `(or nnimap-server-address nnimap-address)'?
>
> (alist (or (gnus-netrc-machine list server port "imap")
> (gnus-netrc-machine list
> (or nnimap-server-address
> nnimap-address)
> port "imap")))
>
> This methods seem preferable than using several authinfo files IMHO
> (and better than introducing an additional server variable). WDYT?
Maybe it is sufficient to just put `server' inside the or statement,
rather than calling gnus-netrc-machine twice? It seems to be
cleaner, if it works.
>> Anyone got a convenient mouse hole somewhere?
>
> I've read your suggestion several times and you convinced me that Gnus
> obviously should behave as you described. :-)
Phew.
Anyhow, server is the server name, so the xyzzy in (nnimap "xyzzy"
...), right? And nnimap-address is the like-named server parameter,
right? But what is nnimap-server-address?
I believe that, given (nnimap "foo" (nnimap-address "bar") ...), Gnus
should first look for a foo entry, then for a bar entry. Not sure if
it should also look for any other entries.
Hm. nnimap-server-address is an obsolete variable, I just see. So
maybe it should be looked at last?
So my proposal, without having tested anything:
(or server nnimap-address nnimap-server-address)
--
This line is not blank.
parent reply other threads:[~2003-06-14 20:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <v98ys5hst8.fsf@marauder.physik.uni-ulm.de>]
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=84llw42yio.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@gmx.net \
/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).