On 22/03/2011 7:21 PM, Bagnoud Thierry [ezwww.ch] wrote:
oups, since 21 mars and not until 21 mars, excuse me bad english :-)
the modification from the rule on 2011-03-21
-header RP_8BIT Return-Path =~ /[^\000-\177]/
+header RP_8BIT Return-Path:raw =~ /[^\000-\177]/
http://svn.apache.org/viewvc/spamassassin/trunk/rulesrc/sandbox/mmartinec/20_misc.cf?r1=906046&r2=906045&pathrev=906046
perhaps the MTA MailScanner is messing up the Return-Path
Thierry Bagnoud
On 3/22/11 5:32 PM, Bagnoud Thierry [ezwww.ch] wrote:
hi,
until 21 mars 2011 after the normal cron.daily/update_spamassassin,
Spamassassin report all messages with the rule RP_8BIT
I don't see this on any inbound email.
what are you saying? you want the rule to be changed to the below?
I don;t see any difference between this rule and your proposed changes
except for the score.
and, I don't recommending changing that score. leave it at 2.866 1.389
2.866 1.389
header RP_8BIT Return-Path:raw =~ /[^\000-\177]/
describe RP_8BIT Return-Path contains 8-bit characters with high bit on
score RP_8BIT 2.8
Thanks to correct this rule.
or are you saying that it is hitting on email that does not have the 8th
bit high?
you might want to post a full email to pastbin.com and send THE LINK
ONLY to this group.
are you saying its a false positive on YOUR system since you like
getting emails with illegal chars in the headers?
then add this to local.cf:
score RP_8BIT 0
Thierry Bagnoud
Something is definitely off. We use SA with MailScanner, and that rule
never hits anything (less than 1 or 2 messages in several thousand).
- Lawrence
