http://bugzilla.spamassassin.org/show_bug.cgi?id=4244
Summary: ALL_TRUSTED misfires when parser thinks it finds a IANA
reserved block
Product: Spamassassin
Version: 3.0.2
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Rules (Eval Tests)
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
I just got a spam message where the Received headers and the server logs
indicated it came from 72.16.62.251.
I was surprised to see ALL_TRUSTED, because I haven't even set trusted networks.
First, I applied the patch from Bug 3949, but when than didn't work, I looked a
bit more into it. I'll attach a file with some debug information in a minute,
but to make a long story short, it thinks 72.16.62.251 is a reserved block. It
isn't, but the IANA reserved block is 172.16/12.
So, it seems like the parser forgets that leading 1 and includes 72.16.62.251 in
the IANA reserved block, causing it to appear trusted, and thus firing the
ALL_TRUSTED. Does that sound like a reasonable conclusion?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
