SA Bugzilla – Bug 2577
Bugzilla's Mail-Domain has no MX
Last modified: 2003-10-14 06:08:26 UTC
Your bugzilla uses 'bugzilla@bugzilla.spamassassin.org' as sender address. This domain has no MX: kurt@leeloo:~> host -t mx bugzilla.spamassassin.org kurt@leeloo:~> nslookup > set q=mx > bugzilla.spamassassin.org. Server: 192.168.0.254 Address: 192.168.0.254#53 Non-authoritative answer: *** Can't find bugzilla.spamassassin.org.: No answer Authoritative answers can be found from: spamassassin.org origin = spamassassin.org mail addr = postmaster.spamassassin.org serial = 2003072901 refresh = 86400 retry = 3600 expire = 604800 minimum = 86400 Therefore our mailserver does not accept mail from your bugzilla: INFO: Connection accepted from bugzilla.spamassassin.org (64.142.3.173) Oct 10, 2003 2:59:12 PM de.ikuag.sponts.filter.DomainHasMX doFilter FINE: domain bugzilla.spamassassin.org has no MX Oct 10, 2003 2:59:12 PM de.ikuag.sponts.action.TarpitAction execute INFO: NO TRANSACTION: tarpitting for 900 seconds This means that a whole bunch of people in the anti-spam community cannot use your bugzilla.
Subject: Re: [SAdev] New: Bugzilla's Mail-Domain has no MX On Fri, Oct 10, 2003 at 06:16:18AM -0700, bugzilla-daemon@bugzilla.spamassassin.org wrote: > Your bugzilla uses 'bugzilla@bugzilla.spamassassin.org' as sender address. This > domain has no MX: ok... > This means that a whole bunch of people in the anti-spam community cannot use > your bugzilla. MX records aren't required. I should set some up though since we have a backup mx for bugzilla...
Subject: Re: [SAdev] New: Bugzilla's Mail-Domain has no MX >Therefore our mailserver does not accept mail from your bugzilla: > >INFO: Connection accepted from bugzilla.spamassassin.org (64.142.3.173) >Oct 10, 2003 2:59:12 PM de.ikuag.sponts.filter.DomainHasMX doFilter >FINE: domain bugzilla.spamassassin.org has no MX >Oct 10, 2003 2:59:12 PM de.ikuag.sponts.action.TarpitAction execute >INFO: NO TRANSACTION: tarpitting for 900 seconds > >This means that a whole bunch of people in the anti-spam community cannot use >your bugzilla. But it does have an A record, which is valid. --j.
You must be kidding, this is definitely a bug in the tarpit. Using an A record is perfectly valid.
I'm closing this as invalid since it 1) has nothing to do with SpamAssassin, and 2) as both quinlan and myself have stated, not having MX records is not an error. However, I did add MX records this morning as bugzilla has a backup host that wouldn't have been used without the records. If you are, in fact, blocking mails from hosts/domains w/out MX records, you're likely getting heavy numbers of false positives. fyi.
Tisk, tisk. Your mail filtering should be based on a more sophisticated set of metrics that involve some sort of... I dunno... weighted scoring of individual factors... perhaps something with an extensible ruleset... I'm just thinking out loud here, of course, there's no such tool. What is SpamAssassin? That... that was a pigeon!