From: Clemens Fischer <ino@despammed.com>
Subject: Re: mail group ('G f') not expiring/shrinking
Date: Thu, 12 Sep 2002 04:22:24 +0200 [thread overview]
Message-ID: <65xcgd5r.fsf@ID-23066.news.dfncis.de> (raw)
In-Reply-To: <vaf1y83wkh4.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> /----
> | `directory'
> | Get mail from several files in a directory. This is typically used
> | when you have procmail split the incoming mail into several files.
> | That is, mail from the file `foo.bar.spool' will be put in the
> | group `foo.bar'. (You can change the suffix to be used instead of
> | `.spool'.) Setting `nnmail-scan-directory-mail-source-once' to
> | non-nil forces Gnus to scan the mail source only once. This is
> | particularly useful if you want to scan mail groups at a specified
> \----
>
> If this is unclear, please suggest improvements.
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.
... until out of other leads to go on i fitted some unimportant folder
with .spool at the end, commented out the :file's and used the
:directory. before that i had thought :file and :directory were just
different means to pick mail-sources. when i read "That is, mail from
the file `foo.bar.spool' will be put in the group `foo.bar'", with the
sentence before that leading in with "typical", i don't see why using
:file is any different.
--
clemens
next parent reply other threads:[~2002-09-12 2:22 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 [this message]
2002-09-12 11:16 ` Kai Großjohann
[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=65xcgd5r.fsf@ID-23066.news.dfncis.de \
--to=ino@despammed.com \
/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).