From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: mail group ('G f') not expiring/shrinking
Date: Thu, 12 Sep 2002 13:16:14 +0200 [thread overview]
Message-ID: <vafelbzcvb5.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <65xcgd5r.fsf@ID-23066.news.dfncis.de>
Clemens Fischer <ino@despammed.com> writes:
> well, i rerad this and many other entries several times, and i reread
> it here in your citation, and if i hadn't experimented, it would still
> not be clear to me (although you even suggested using :directory in
> private email, but with no apparent reason). why not tell people:
> "using :directory will prohibit gnus from further splitting the
> mail-source, but it will do so when using :file." i want that to be
> clearly stated, because at that time i had many old mbox-type folders
> in the incoming directory, some of which where prefiltered by
> procmail. also, those files did not have any distinguishing marks
> like some suffix. this made me think i should rather use the :file
> attribute to be more picky.
Now there is another paragraph after the one you cited:
/----
| There is also the variable `nnmail-resplit-incoming', if you set
| that to a non-nil value, then the normal splitting process is
| applied to all the files from the directory, *Note Splitting
| Mail::.
\----
Does that make it clearer?
kai
--
~/.signature is: umop 3p!sdn (Frank Nobis)
next prev parent reply other threads:[~2002-09-12 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86k7m0c50o.fsf@number6.magda.ca>
[not found] ` <vafbs7bicuq.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <lm6caxgz.fsf@ID-23066.news.dfncis.de>
[not found] ` <vaf65xfwkkp.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <vaf1y83wkh4.fsf@lucy.cs.uni-dortmund.de>
2002-09-12 2:22 ` Clemens Fischer
2002-09-12 11:16 ` Kai Großjohann [this message]
[not found] ` <ofb04ne8.fsf@ID-23066.news.dfncis.de>
[not found] ` <vafadmjdnoi.fsf@lucy.cs.uni-dortmund.de>
[not found] ` <m34rcqrl1u.fsf@multivac.cwru.edu>
2002-09-16 19:47 ` Kai Großjohann
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=vafelbzcvb5.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).