Gnus development mailing list
 help / color / mirror / Atom feed
From: David Hanak <dhanak@inf.bme.hu>
Subject: Re: multiple nnmbox groups?
Date: Tue, 30 Sep 2003 11:02:20 +0200	[thread overview]
Message-ID: <m2d6dizm1v.fsf@maui.hanak.hu> (raw)
In-Reply-To: <m3d6dj592m.fsf@fischman.org>

On Tue, 30 Sep 2003, Ami Fischman wrote:

> Is it possible to have multiple nnmbox groups in a single gnus setup?  I
> can't seem to figure out how to create a group that uses nnmbox as the
> backend AND uses a particular file as its data source.
>
> The reason I want this is that I have procmail filter out certain things
> for certain reasons into separate mbox files.  Currently I have several
> nndoc groups, each of which comes from one mbox file, but
> ticks/marks/expiry/read status doesn't seem to get saved except in the
> adaptive scoring files.  So, a way to make nndoc remember my marks between
> sessions would be just as good.

What you are looking for is nnfolder (basically mbox format with a few
additional headers).  But splitting with procmail into groups which are
modified simultaneously by Gnus is not a very good idea.  For one, there is
the problem of locking, this can be solved.  For another, Gnus uses so
called active files to speed up group access, where it stores the index
number of the first and last articles.  If procmail appends a few messages
to a group, it will not be noticed by Gnus, unless you set
`nnfolder-ignore-active-file' to t, but then you lose the speed-up.

I suggest you use nnmail-split-fancy as nnmail-split-methods, it can do
everything procmail can.  If you still want to use procmail, use nnmaildir
instead, which allows simultaneous read and write access and doesn't use
active files.

David



      reply	other threads:[~2003-09-30  9:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-30  2:00 Ami Fischman
2003-09-30  9:02 ` David Hanak [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=m2d6dizm1v.fsf@maui.hanak.hu \
    --to=dhanak@inf.bme.hu \
    /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).