Bug 6507 - rule ALL_TRUSTED hits for all mails
Summary: rule ALL_TRUSTED hits for all mails
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: 3.3.1
Hardware: HP Linux
: P2 major
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-04 09:41 UTC by matt
Modified: 2010-11-04 11:57 UTC (History)
2 users (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description matt 2010-11-04 09:41:58 UTC 
We have set all of our mx/relay ip addresses to "trusted_networks".
We have set all of our ip addresses to "internal_networks".

But spamassassin decides, that for example the external ip 82.128.10.151 is trusted and internal:

Nov  4 11:43:55.174 [16865] dbg: received-header: parsed as [ ip=82.128.10.151 rdns=ml82.128.10.151.multilinks.com helo=ml82.128.10.151.multilinks.com by=<our-mx> ident= envfrom= intl=0 id=oA4A15tq025501 auth= msa=0 ]
Nov  4 11:43:55.175 [16865] dbg: received-header: relay 82.128.10.151 trusted? yes internal? yes msa? no

The rule ALL_TRUSTED hits for all of our incoming mails! So we get hundreds of false negatives a day.

Setup: SA 3.3.1, NetAddr::IP 4.0.35
Comment 1 Justin Mason 2010-11-04 10:00:20 UTC 
can you downgrade NetAddr::IP?  this is a regression they introduced in 4.0.35. I understand they're working on fixing it....
Comment 2 matt 2010-11-04 10:56:09 UTC 
Rollback to NetAddr::IP 4.033 solved the issue.
Comment 3 Mark Martinec 2010-11-04 11:57:41 UTC 
> Rollback to NetAddr::IP 4.033 solved the issue.

Indeed.
The NetAddr::IP 4.034 and NetAddr::IP 4.035 are broken, see:

  https://rt.cpan.org/Public/Bug/Display.html?id=62521