Bug 2806 - Wrong usage of SORBS DNSBL
Summary: Wrong usage of SORBS DNSBL
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Rules (show other bugs)
Version: 2.60
Hardware: PC Linux
: P5 normal
Target Milestone: 3.0.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-04 00:11 UTC by Michel Bouissou
Modified: 2004-03-03 12:32 UTC (History)
1 user (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 Michel Bouissou 2003-12-04 00:11:34 UTC 
Hi there, 
 
I've noticed that quite a number of legitimate messages that I receive trigger 
the RCVD_IN_SORBS rule with a SORBS 127.0.0.10 result. 
 
But 127.0.0.10 in SORBS means "DIALUP/DYNAMIC", thus 127.0.0.10 SORBS result 
should be taken into account only when a DYNABLOCK or other DUL listing would 
be. 
Currently, it seems that SORBS 127.0.0.10 is taken into account in any case 
(which means even if the dialup/dynamic origin didn't sent direct-to-MX mail). 
 
This of course, is a wrong behaviour, but doesn't make such a big issue as 
SORBS currently has a quite low default score in SA. 
 
Cheers.
Comment 1 Rich Puhek 2004-02-18 22:19:40 UTC 
Are the legitimate messages coming from something that should be in
trusted_networks? If so, it may look like direct to MX mail to SA.
Comment 2 Justin Mason 2004-03-03 21:32:32 UTC 
this is already fixed in 3.0.0