From: Doug Alcorn <doug@lathi.net>
Subject: nnmail-split-methods confusion
Date: 21 Feb 2001 12:00:42 -0500 [thread overview]
Message-ID: <m3vgq43r9h.fsf@localhost.localdomain> (raw)
I'm trying to prevent any html formatted mail message from ending up
in my various folders. The common denominator in all the offending
messages is the content-type. I thought I could just add a filter in
the split methods for this. Here's what I have:
(setq nnmail-split-methods
'(("html-junk" "^Content-Type: multipart/alternative")
("yahoo" "^X-Gnus-Mail-Source.*yahoo\\.com")
("inbox" "")))
Unfortunately, this causes the offending messages to end up in _both_
"html-junk" and either "yahoo" or "inbox". I thought that
nnmail-split-methods worked kindof like procmail: once a rule is
matched it quits appling rules.
--
(__) Doug Alcorn (mailto:doug@lathi.net http://www.lathi.net)
oo / PGP 02B3 1E26 BCF2 9AAF 93F1 61D7 450C B264 3E63 D543
|_/ If you're a capitalist and you have the best goods and they're
free, you don't have to proselytize, you just have to wait.
next reply other threads:[~2001-02-21 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 17:00 Doug Alcorn [this message]
2001-02-21 17:13 ` ShengHuo ZHU
2001-02-21 17:14 ` Laura Conrad
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=m3vgq43r9h.fsf@localhost.localdomain \
--to=doug@lathi.net \
/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).