On 23 May, Andrew Edelstein wrote:
| On Thu, May 23, 2002 at 10:10:04AM -0400, Don Hammond wrote:
| > My procmail recipes start with checking for one of my own X-Loop:
| > headers, in which case it immediately goes to $DEFAULT (with an
| > X-Loop Notice to me), followed by identifying MAILER-DAEMON/Postmaster,
| > then local and list mail before even thinking about spam filtering,
|
| That's interesting. I find that I have to filter list mail first, then
| MAILER-DAEMON. Otherwise most list messages will be caught by the DAEMON
| filter.
Sorry for a less than prompt reply. I wrote that off the top of my head
on my way out the door yesterday morning. It was also a less than
precise description. The testing for MAILER-DAEMON/Postmaster messages
is not a rigorous test for all such messages. It's more accurately
part of identifying locally generated messages. Bottom line is I don't
use the built-in ^FROM_DAEMON reg exp for this task, so it doesn't match
Precedence: bulk (or anything else) in list messages.
--
Reply to list please, or append "6" to "procmail" in address if you must.
Spammers' unrelenting address harvesting forces me to this...reluctantly.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail