Thanks a bunch, Sam. BTW, what are the chances of getting in an enhancement to the DENIED_RBL_MATCH log messages that would include the name of the BL which matched? I'd really like to glean this from the logs on a regular basis, so I'd rather not increase the log verbosity. Something like: DENIED_RBL_MATCH at: zen.spamhaus.org from: ... What do you think?
Thanks again. -- -Eric 'shubes' On 03/11/2011 12:45 PM, Sam Clippinger wrote: > Interesting... I think I understand what's happening. > > spamdyke is trying to find the MX record for bounce.e.groupon.com and > receives an MX response that says "bounce-mx.exacttarget.com". Then it > tries to find an IP address for bounce-mx.exacttarget.com by searching > for A or CNAME records. Or rather, that's what it should do. Due to an > oversight on my part, it searches for A, CNAME and MX records because I > was lazy and sent the same list of types to the function that tries to > find the IP that was used to find the MX. > > As it happens, bounce-mx.exacttarget.com has both an A and a MX record > associated with it, which is legal (but stupid). When spamdyke receives > the MX record it asked for but didn't expect, it assumes the remote > nameserver is broken and stops with an error. Due to a second oversight > on my part, that error triggers the filter instead of failing gracefully. > > So, two bugs. I'll get them fixed. :) Thanks for reporting this! > > -- Sam Clippinger > > On 3/11/11 10:51 AM, Eric Shubert wrote: >> 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. >> >> _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
