Procmail isn't misfiltering anything. It is doing exactly what you've told
it to do, which is to take any message which includes certain recipients
and dump it into a certain folder - even when that message hasn't been
delivered from that list.
At 21:20 2002-01-25 +0000, Ian Chilton wrote:
I use procmail to filter my mailinglists which all go to
mailinglist(_at_)ichilton(_dot_)co(_dot_)uk(_dot_) If someone posts to more
than 1 list I am
subscribed too, I get 2 copies in the mailbox which is highest up in the
procmail rules file and no post in the one which is lower down.
Is there a way to overcome this?
Apparently the following comment didn't register, although it was offered
in direct response to your problem:
Filtering on lists generally involves checking the sender or some other
field which should be list specific. Then, you're filtering based on the
copy delivered by the list itself, not merely based on the fact that the
list was a recipient. This also allows you to pick out messages which
were delivered to certain mailing lists as BCC:
If you use ^TO, it will match on each message where the address in the
expression matches a known recipient field in the message. Whereas if you
use Sender, or some other header which should be unique to the list SENDING
you this particular _copy_ of the message, then it'll only be filtering
those messages you receive FROM that *list server* (of which, for any
multiple-list delivered message, you should only be recieving
one). Anything left over after you've filtered lists in such a way is a
copy addressed directly to you (either in cleartext or as a BCC), or is
coming through a list you're subscribed to, but not actually filtering.
If you can't manage the limited work involved with doing that, then AT A
MINIMUM, move the recipes using ^TO *AFTER* those using the more positive
matching ^Sender - that way, at least those messages delivered by those
(^Sender) lists will be positively filed, and you'll end up with less
misfiled mail.
The proper way to handle mailing lists still remains filtering based on
where the message was sent from.
:0:
* ^TO_freebsd-stable(_at_)freebsd(_dot_)org
freebsd-stable
Besides the plethora of other headers on list messages, what is wrong with
either of the following two?
Sender: owner-freebsd-stable(_at_)FreeBSD(_dot_)ORG
List-ID: <freebsd-stable.FreeBSD.ORG>
:0:
* ^TO_.*sunhelp.org
sunhelp
I've never subscribed, but I'd be surprised if Bill didn't use a standard
mailing list package, which would set a Sender header.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail