in message
<5(_dot_)1(_dot_)1(_dot_)6(_dot_)2(_dot_)20021210084459(_dot_)092febe0(_at_)mail(_dot_)professional(_dot_)org>,
wrote Professional Software Engineering thusly...
Here's a sampling of Message-ID based recipes I use:
...
thanks sean. i already had some of the recipes, but didn't even
think about the others, especially message-id being same as the from
address.
once i put a recipe to check the RHS of @ to be at least of
"some.thing" form. and that caught far too many otherwise wanted
messages. it was quite a pain to move all the messages caught in
appropriate folders.
while people are contributing, let me too...
# extract message-id:
:0
* Message-ID:[ ]*.+\/<(_dot_)+(_at_)(_dot_)+>
{ msg_id = "$MATCH" }
:0 E:
Ignore/xx.spam
...currently i use $msg_id only for LOGging, but now i will also
create recipes to check if it matches From:, References: and
In-Reply-to: headers. in addition, i will need to tighten up the
above recipe.
- parv
--
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail