From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: nnfolder has me baffled
Date: Fri, 12 May 2000 19:38:25 +0200 (MET DST) [thread overview]
Message-ID: <200005121738.TAA12990@marcy.cs.uni-dortmund.de> (raw)
In-Reply-To: merlyn@stonehenge.com's message of "12 May 2000 08:22:57 -0700"
merlyn@stonehenge.com (Randal L. Schwartz) writes:
> So, I tried G-M'ing a group with "arch.todo" "nnfolder". It created a
> directory ~/Mail/arch/todo (note, NOT under ~/Mail/archive),
This is the right thing for Gnus to do, since it has two servers,
`nnfolder+archive' and `nnfolder', and you chose the second one.
> which nnml on next invocation decided was an nnml group. It also
> took about three or four tries to get everyone to agree that the
> folder wasn't there again.
This is because two of your backends (nnml and nnfolder) share the
same active file, and each gets confused by the other's groups.
You may wish to frob your nnfolder server to have a different active
file. It might be best to locate your nnfolder server in a different
directory altogether, though I'm not sure if this is necessary. (I
avoid multiple servers using the same directory :-)
kai
--
Beware of flying birch trees.
prev parent reply other threads:[~2000-05-12 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-12 15:22 Randal L. Schwartz
2000-05-12 15:36 ` Shenghuo ZHU
2000-05-12 15:47 ` Randal L. Schwartz
2000-05-12 16:06 ` Shenghuo ZHU
2000-05-12 18:49 ` Randal L. Schwartz
2000-05-12 20:22 ` Jaap-Henk Hoepman
2000-05-17 14:16 ` mail backend directories (was: nnfolder has me baffled) Toby Speight
2000-05-12 17:39 ` nnfolder has me baffled Kai Großjohann
2000-05-12 18:01 ` Randal L. Schwartz
2000-05-12 19:19 ` Kai Großjohann
2000-05-12 19:26 ` David S. Goldberg
2000-05-12 17:38 ` Kai Großjohann [this message]
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=200005121738.TAA12990@marcy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).