I did a detail log, and captured one of these. It says:
ERROR: DNS response for bounce-mx.exacttarget.com: expected type A, 
CNAME but received type MX
FILTER_SENDER_NO_MX domain: bounce.e.groupon.com

 From the spamassassin host, I get:
[shubes@tacs-mail ~]$ host bounce-mx.exacttarget.com
bounce-mx.exacttarget.com has address 66.231.91.236
bounce-mx.exacttarget.com mail is handled by 10 bounce-mx.exacttarget.com.
[shubes@tacs-mail ~]$

I don't see anything wrong here (but could be misunderstanding 
something). Is spamdyke getting an MX record back before a type A (or 
CNAME) record? Is a wildcard perhaps involved somehow?

One other thing. I'm under the impression (from the dyndns.com site) 
that MX records can (should?) not point to CNAME records. If this is 
indeed true, then I would think that spamdyke shouldn't be looking for a 
CNAME record which corresponds to the MX (as indicated in the message).

As always, thanks Sam.

-- 
-Eric 'shubes'

On 02/26/2011 01:32 PM, Sam Clippinger wrote:
> I can't reproduce this; when I try those addresses it works fine for
> me.  Can you try two things?  First, run "host reply.ticketmaster.com"
> to see if your server can find the MX record there -- the records for
> ticketmaster.com aren't actually checked.  Second, can you enable
> excessive output and full logging to see what's happening during these
> deliveries?  Excessive output should show all of the DNS packets that
> are sent and received.
>
> -- Sam Clippinger
>
> On 2/25/11 3:05 PM, Eric Shubert wrote:
>> Running the latest spamdyke 4.2.0+TLS+CONFIGTEST+DEBUG on CentOS5.4 x86,
>> Using caching-nameserver on localhost, and I'm not seeing any named
>> errors in the system log.
>>
>> I just happened to notice this in my smtp log:
>>
>> 02-25 13:54:30 spamdyke[32582]: DENIED_SENDER_NO_MX from:
>> ntf-330906_53-9098559-ticketmaster_=_shubes....@reply.ticketmaster.com
>> to: ticketmas...@shubes.net origin_ip: 209.104.37.138 origin_rdns:
>> vg138.ntf.els4.ticketmaster.com auth: (unknown) encryption: TLS
>>
>> Seemed odd, so I checked:
>> # host ticketmaster.com
>> ticketmaster.com has address 209.104.34.32
>> ticketmaster.com has address 209.104.41.32
>> ticketmaster.com has address 209.104.45.32
>> ticketmaster.com has address 209.104.56.26
>> ticketmaster.com has address 209.104.58.151
>> ticketmaster.com has address 209.104.59.96
>> ticketmaster.com mail is handled by 10 mx.chi.ticketmaster.com.
>> ticketmaster.com mail is handled by 10 mx.els.ticketmaster.com.
>>
>> Am I missing something, or is there a bug?
>>
>>


_______________________________________________
spamdyke-users mailing list
spamdyke-users@spamdyke.org
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Reply via email to