On 22/03/11 23:28, Lawrence @ Rogers wrote:
Something is definitely off. We use SA with MailScanner, and that rule never hits anything (less than 1 or 2 messages in several thousand).
My guess would be that you aren't using MailScanner with Sendmail whereas the original poster is.
I've been hit by this issue; it's nothing to do with the rule misfiring - it's more of a conceptual issue of how MailScanner works e.g. by taking the queue file and moving it from an inbound to and outbound spool and then forcing a delivery.
In the Sendmail queue files, there is always a 'Return-Path:' header that is a placeholder for expansion should Sendmail be delivering the message to a mailer that specifies that it requires a Return-Path header (e.g. local/procmail etc.); however as the header is in the queue file, MailScanner still reads it in as a regular header and it therefore gets passed to SpamAssassin when the message is checked. Unfortunately the placeholder used by Sendmail contains a high-bit character which then causes this rule to fire.
Regards, Steve.
