From: Boris DAIX <Boris.Daix@insa-lyon.fr>
Subject: Re: fancy splitting and procmail
Date: Wed, 03 Jul 2002 18:58:02 +0200 [thread overview]
Message-ID: <87sn30wxyd.fsf@Pulsar.resI.insa-lyon.fr> (raw)
In-Reply-To: <afuvmh$n6s$1@wsc10.lrz-muenchen.de>
Adrian Kubala <kubalaa@eikon.tum.de> writes:
> Ooh, ohh, I wanna answer! I just had this explained to me, so I'll see if I
> can explain it on to you. Someone else can probably do it better, but maybe
> this will be enough for you to go on.
Thanks a lot :-)
> Boris DAIX <Boris.Daix@insa-lyon.fr> wrote:
>> (setq mail-sources '((directory :path "~/spool/")
>> (file :path "/var/spool/mail/bdaix")))
>
> Okay, so this means each file in ~/spool goes to a separate group without
> being split, while messages in your /var spool file go through the normal
> splitting. I.e. ~/spool/list.debian-foo.spool goes automatically to
> nnml+private:list.debian-foo.
>
>> But now, I'd like to split the whole stuff better, within gnus, I tried
>> adding.
>
> Okay, so you want to stop auto-splitting the procmail spools, and split them
> manually instead. To do that, you can try "nnmail-resplit-incoming" (though
> maybe this doesn't work in Oort?), or change "directory" to a bunch of "file"
> entries, one for each procmail spool. File entries are always split, directory
> entries aren't.
>
> Then, to manually achieve the same effect as auto-splitting, use the header
> "X-Gnus-Mail-Source" in your split:
What does this mean ? I was ok 'till there... ;-) I'll try it but if
someone knows what it means...
> (setq mail-sources '((file :path "/var/spool/mail/krid")
> (file :path "/home/krid/Mail/IN.list")
> (file :path "/home/krid/Mail/IN.spam")))
>
> (setq nnmail-split-fancy
> '(|
> [..]
> ("X-Gnus-Mail-Source" "IN.list" "list.misc")
> [..]
>
> (courtesy of Dirk Bernhardt)
>
> -Adrian
Thanks a lot again !
Boris
next parent reply other threads:[~2002-07-03 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y9ctxh3l.fsf@Pulsar.resI.insa-lyon.fr>
[not found] ` <afuvmh$n6s$1@wsc10.lrz-muenchen.de>
2002-07-03 16:58 ` Boris DAIX [this message]
[not found] ` <afvb1r$2bj$1@wsc10.lrz-muenchen.de>
[not found] ` <87bs9olniq.fsf@Pulsar.resI.insa-lyon.fr>
2002-07-04 14:57 ` Kai Großjohann
2002-07-03 20:18 ` Boris DAIX
2002-07-03 20:30 ` Josh Huber
2002-07-03 20:49 ` Jack Twilley
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=87sn30wxyd.fsf@Pulsar.resI.insa-lyon.fr \
--to=boris.daix@insa-lyon.fr \
/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).