From: Uwe Brauer <uwe_brauer@mat.ucm.es>
Cc: ding@gnus.org
Subject: Re: various independent "mail servers" and the nnml backend
Date: Tue, 19 Jul 2005 21:11:50 +0000 [thread overview]
Message-ID: <87u0iq1ox5.fsf@mat.ucm.es> (raw)
In-Reply-To: <4nzmsix4ms.fsf@lifelogs.com>
>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:
Ted> On Mon, 18 Jul 2005, uwe_brauer@mat.ucm.es wrote:
>>>>>>> "Ted" == Ted Zlatanov <tzz@lifelogs.com> writes:
>>
Ted> They shouldn't. Try the `a' `e' method to add the servers instead of
Ted> gnus-secondary-select-methods. Unfortunately I don't have this set up
Ted> myself, so I can't vouch for the correctness of Gnus with two nnml
Ted> servers, but if you run into further problems I'll take a look to make
Ted> 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.
>>
I just deleted all my .newsrc newsrc.eld files and restarted gnus, I
add a nnml server,
so the corresponding buffer looks like
(nnml "NNML")
However independent whether I edit the server in order to obtain something
like this
(nnml "NNML-Archive" (nnml-directory "/home/oub/Mail/NNML-Archive"))
When I enter the nnml server he shows me groups which do not exist. So
for some reason gnus reads some old information which resulted from my
experiments. But what.
Another question: it seems that I can use the secondary select method
in order to select a server, but I could also to it in the way
described above, even for nnimap or nntp servers. Which method is
better?
Thanks
Uwe
next prev parent reply other threads:[~2005-07-19 21:11 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
2005-07-19 17:03 ` Uwe Brauer
2005-07-19 19:36 ` Uwe Brauer
2005-07-19 21:11 ` Uwe Brauer [this message]
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=87u0iq1ox5.fsf@mat.ucm.es \
--to=uwe_brauer@mat.ucm.es \
--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).