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: [email protected] 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 [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
