Bug 2577 - Bugzilla's Mail-Domain has no MX
Summary: Bugzilla's Mail-Domain has no MX
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Documentation (show other bugs)
Version: unspecified
Hardware: Other other
: P5 normal
Target Milestone: 2.70
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-10 06:07 UTC by Kurt Huwig
Modified: 2003-10-14 06:08 UTC (History)
0 users



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description Kurt Huwig 2003-10-10 06:07:01 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.
Comment 1 Theo Van Dinter 2003-10-10 06:20:03 UTC
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...

Comment 2 Justin Mason 2003-10-10 11:23:31 UTC
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.

Comment 3 Daniel Quinlan 2003-10-10 11:46:01 UTC
You must be kidding, this is definitely a bug in the tarpit.
Using an A record is perfectly valid.
Comment 4 Theo Van Dinter 2003-10-10 11:56:40 UTC
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.
Comment 5 Aaron Sherman 2003-10-14 14:08:26 UTC
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!