Cris Collins wrote:
Using the below rules I am catching alot of SPAM, however even one
of the rules matches some get through. For instance a large mailing
comes in a few individuals well forward me copies of SPAM that I
have recorded in either Procmail.head, or SPAM. Can someone explain
how some are getting through?
Do you have some example headers? Hard to tell otherwise. A few
remarks, though:
:0:
* ^Subject:.*xxx
{
:0Ah:/export/home/clc/Procmail.head.lock
| cat >> /export/home/clc/Procmail.head
}
Is there any reason not to make that simply
:0 h:
* ^Subject:.*xxx
/export/home/clc/Procmail.head
? Likewise for the other recipes of that kind.
# No To: line
:0
* !^To:
$SPAM
":0:" would be better.
:0:
* ^To:.*Undisclosed.recipients@
{
:0Ah:/export/home/clc/Procmail.head.lock
| cat >> /export/home/clc/Procmail.head
}
:0:
* ^To:.*Undisclosed.Recipients@
{
:0Ah:/export/home/clc/Procmail.head.lock
| cat >> /export/home/clc/Procmail.head
}
Case doesn't matter without the "D" flag, so you can omit the second
one.
# The "To:" line is empty
:0
* ^To: $
$SPAM
# The "From:" line is empty
:0
* ^From: $
$SPAM
":0:" again, and note that these don't catch lines that end
immediately after the colon, without a trailing space.
/HW
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail