You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2004/02/18 19:20:25 UTC

[Bug 3058] New: Problem with people who have dynamic IP from there ISP

http://bugzilla.spamassassin.org/show_bug.cgi?id=3058

           Summary: Problem with people who have dynamic IP from there ISP
           Product: Spamassassin
           Version: unspecified
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Rules (Eval Tests)
        AssignedTo: spamassassin-dev@incubator.apache.org
        ReportedBy: nickg@anhosting.com


Alot of innocent victims are getting blocked because there respectible large 
ISP has a spammer on 1 IP out of a few million.  This gets the /13 or how ever 
many they have on the SORBS RBL and causes email blocking for the spammer plus 
millions of others.  For instance I know a guy who uses Comcast and has his ip 
BL'ed

SpamAssassin can be configured to use or not use specific DNS BLs. You should 
configure it, or at least have an option to NOT use BLs that check if a SMTP 
connection comes from a dynamically-allocated IP address from at least the 
largest ISP's.

Please understand that I have called Comcast (my ISP) and ask them to get my 
dynamic IP address removed from a list of dynamic addresses, they refused to 
do so. I am using a dynamic IP address. Dynamic IP addresses are not �bad�. 
The maintainers of lists of dynamic address lists (e.g. MAPS DUL) would never 
be convinced to remove an actual dynamic IP from their list just because it 
inconveniences a user. If they did, their list would become less reliable, and 
therefore less valuable.

We�re dealing with a configuration issue here � one that spam assassins 
administrators need to work on. SpamAssassin can be configured to not 
disqualify messages originating from a dynamically allocated IP address. I�m 
sure you can find someone within your company who can figure out how.

Thanks in advance for fixing this!



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Re: [Bug 3058] New: Problem with people who have dynamic IP from there ISP

Posted by Rich Puhek <rp...@etnsystems.com>.

bugzilla-daemon@bugzilla.spamassassin.org wrote:
> 
> Alot of innocent victims are getting blocked because there respectible large 
> ISP has a spammer on 1 IP out of a few million.  This gets the /13 or how ever 
> many they have on the SORBS RBL and causes email blocking for the spammer plus 
> millions of others.  For instance I know a guy who uses Comcast and has his ip 
> BL'ed
> 
> SpamAssassin can be configured to use or not use specific DNS BLs. You should 
> configure it, or at least have an option to NOT use BLs that check if a SMTP 
> connection comes from a dynamically-allocated IP address from at least the 
> largest ISP's.
> 
> Please understand that I have called Comcast (my ISP) and ask them to get my 
> dynamic IP address removed from a list of dynamic addresses, they refused to 
> do so. I am using a dynamic IP address. Dynamic IP addresses are not “bad”. 
> The maintainers of lists of dynamic address lists (e.g. MAPS DUL) would never 
> be convinced to remove an actual dynamic IP from their list just because it 
> inconveniences a user. If they did, their list would become less reliable, and 
> therefore less valuable.
> 
> We’re dealing with a configuration issue here – one that spam assassins 
> administrators need to work on. SpamAssassin can be configured to not 
> disqualify messages originating from a dynamically allocated IP address. I’m 
> sure you can find someone within your company who can figure out how.
> 
> Thanks in advance for fixing this!
> 

Well, MAPS defaults to score of 0 (never check). Most of the sorbs lists 
are scored pretty low.

I believe we shouldn't have an issue if:

  1) The users on the dynamic IP are sending through their ISP's SMTP relay.
  2) Trusted networks is set correctly
  3) Trusted networks works properly (open bugs on this, I believe?)
  4) SA is aware that the RBL in question is a "dialup" type list.

I believe the way SA is supposed to work in this case is: "ok, someone 
at 1.2.3.4.dynamic.big.isp sent mail though mx-relay.big.isp. Since they 
went through a relay, I don't care if 4.3.2.1 is on a dynamic IP RBL".

If you are on a dynamic list, and are not sending through a relay, well, 
that is a problem...

Correct, a maintainer of a dynamic IP rbl is not going to remove and IP 
from a list because of your inconvenience... if they did, you'd have to 
call them every time you changed your IP!

--Rich