|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Better way to match headers
From: Noel Jones (njones
megan.vbhcs.org)
Date: Mon Jan 02 2006 - 15:05:25 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
At 02:11 PM 1/2/2006, Joey wrote:
>Currently I am matching in header_checks things like this:
>header_checks = regexp:/etc/postfix/header_checks
>
>File contains things like this:
>
>/^(To|From|Cc|Reply-To):.*emailoffernetwork\.com/ REJECT
>Header TFCR 1060
>/^(To|From|Cc|Reply-To):.*ideasforthegoodlife\.com/ REJECT
>Header TFCR 1061
The above are probably better matched using a
check_sender_access or check_client_access map. As a
general rule, try to limit use of header_checks to those
things you can't match otherwise for performance reasons.
Also, if you have checks for similar items, such as many
Subject: tests, you can enclose them in an IF/ENDIF section
to improve performance.
>/^Subject:.*Weight Loss Pills/ REJECT SubJect
>Rejected
>/^Subject:.*STOP SNORING IMMEDIATELY/ REJECT
>SubJect Rejected
>
This is the right place to block a message by subject, but
it's been my experience that blocking by subject is an
exercise in wasted time. There are simply too many "bad"
subjects and they change too fast.
Instead look for other things such as a client, HELO or
sender to block, or investigate using one or more of the
popular RBLs, or look into using SpamAssassin.
--
Noel Jones
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]