From: Karl Eklund <kekn@medelklassen.com>
Subject: Using ifile as a last resort
Date: 10 Feb 2003 20:17:47 +0100 [thread overview]
Message-ID: <87adh4t06c.fsf@medelklassen.com> (raw)
This is the way I split mail. ifile-gnus is set to "spam filter only"
mode.
(setq nnmail-split-fancy
'(|
("X-Mailing-List" "\\(debian-.*\\)@lists.debian.org" "list.\\1")
("List-Id" "bugtraq\.list-id\.securityfocus\.com" "list.bugtraq")
("List-Id" "elektrosmog\.nu" "list.elektrosmog")
("List-Id" "selinux-aktiva\.se\.linux\.org" "list.selinux-aktiva")
("List-Id" "ifile-discuss\.nongnu\.org" "list.ifile-discuss")
("List-Id" "full-disclosure\.lists\.netsys\.com"
"list.full-disclosure")
("List-Id" "spyce-users\.lists\.sourceforge\.net" "list.spyce-users")
("Mailing-List" "contact sslug-announce-help@sslug\.dk; run by ezmlm"
"list.sslug-announce")
(: ifile-spam-filter
"mail.misc")))
ifile takes a while so I don't want to run it on the mailing lists,
only on everything that isn't caught by the mailing list filters. I
think it runs on every message now. Is there some obvious error? I
must confess I don't have a profound understanding of "fancy
splitting".
Another question: if I put in < and > around the regexps (the List-Id
header looks that way), everything ends up in the mail.misc. \< \> or
\\< \\> don't work either. Do plain < > really have a meaning in
regexps?
next reply other threads:[~2003-02-10 19:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 19:17 Karl Eklund [this message]
2003-02-11 9:24 ` Stefan Bodewig
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=87adh4t06c.fsf@medelklassen.com \
--to=kekn@medelklassen.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).