From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: various independent "mail servers" and the nnml backend
Date: 19 Jul 2005 10:16:43 -0400 [thread overview]
Message-ID: <4nzmsix4ms.fsf@lifelogs.com> (raw)
In-Reply-To: <87wtnongzq.fsf@mat.ucm.es> (Uwe Brauer's message of "Mon, 18 Jul 2005 17:47:37 +0000")
On Mon, 18 Jul 2005, uwe_brauer@mat.ucm.es wrote:
>>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:
>
> Ted> On Mon, 18 Jul 2005, oub@mat.ucm.es wrote:
> >> How can I define two independent servers with the nnml backend.
>
> Ted> This should work:
>
> Ted> (add-to-list 'gnus-secondary-select-methods
> Ted> '(nnml "POP3-GMX" (nnml-directory "/home/oub/Mail/POP3-GMX"))
> Ted> '(nnml "OTHER" (nnml-directory "/home/oub/Mail/OTHER")))
>
> Right, ok thanks. The only odd thing is that the groups in POP3-GMX
> get mirrored in OTHER. I don't know why.
They shouldn't. Try the `a' `e' method to add the servers instead of
gnus-secondary-select-methods. Unfortunately I don't have this set up
myself, so I can't vouch for the correctness of Gnus with two nnml
servers, but if you run into further problems I'll take a look to make
sure the underlying code is doing the right thing.
> Ted> You can also do `a' from the Server buffer, add an nnml server, then
> Ted> hit `e' to edit the parameters and add the nnml-directory.
>
> Ok, but it seems that I can't edit an existing server this way.
If a server is defined by Lisp code, rather than through the `a'
method I mentioned, you can't edit the parameters through the `e'
command in the Server buffer.
Ted
next prev parent reply other threads:[~2005-07-19 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 16:09 Uwe Brauer
2005-07-18 15:22 ` Ted Zlatanov
2005-07-18 17:47 ` Uwe Brauer
2005-07-19 14:16 ` Ted Zlatanov [this message]
2005-07-19 17:03 ` Uwe Brauer
2005-07-19 19:36 ` Uwe Brauer
2005-07-19 21:11 ` Uwe Brauer
2005-07-19 19:54 ` David Z Maze
2005-07-20 19:14 ` Uwe Brauer
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=4nzmsix4ms.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).