Bug 1403 - check to see if the mx of a domain is 127.0.0.1 or a private number
Summary: check to see if the mx of a domain is 127.0.0.1 or a private number
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: 2.43
Hardware: All All
: P4 enhancement
Target Milestone: 2.60
Assignee: Daniel Quinlan
URL:
Whiteboard:
Keywords: dns
Depends on: 1455
Blocks:
  Show dependency tree
 
Reported: 2003-01-22 10:43 UTC by Jason Portwood
Modified: 2003-04-30 14:27 UTC (History)
0 users


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 Jason Portwood 2003-01-22 10:43:51 UTC 
Testing to see if the MX of a domain is 127.0.0.1 - or really 127.0.0.0/8
as well a private network number.
Comment 1 Allen Smith 2003-01-22 12:44:49 UTC 
Thanks. I'd thought of that, actually, and since my new DNS code gets IP
addresses from the additional section of packets, it should not be difficult to
do efficiently with NO_MX_FOR_FROM. Will work on after the new DNS code is
made a bit faster.

	-Allen
Comment 2 Daniel Quinlan 2003-04-30 22:15:47 UTC 
I'm looking into this bug now that the DNS code is stable again.
Comment 3 Daniel Quinlan 2003-04-30 22:27:44 UTC 
Okay, I only got 8 hits for 3000 recent spam (0.26%).  Justin notes that
it's probably just as easy for a spammer to pick a random address.  0.26%
is not high enough to justify the test IMO.

In addition, most of these are listable in dsn.rfc-ignorant.org, so hopefully
they'll get caught there.  So, I'm closing this.