Interesting - as long as mail.sending-domain.com has an A record, it shouldn't NEED to have a MX record. I agree that DENIED_SENDER_NO_MX should apply to the envelope sender (i.e., From header) domain and not the rDNS for the sender's IP.
I guess this is why I added "reject-missing-sender-mx=no" to my spamdyke config. Ideally, I'd like to turn it on, but I probably discovered the behavior you're talking about and had to turn it off ... On 5/12/11 9:22 AM, Faris Raouf wrote: > Basically an email fromsome...@sending-domain.com to > u...@local-domain.com was DENIED_SENDER_NO_MX (sending IP's rDNS was > mail.sending-domain.com) > > sending-domain.com DOES have an MX record but mail.sending-domain.com does > not. > > I had always thought that the MX lookup applies to sending-domain.com and > not to the rDNS of the sending IP. My logic is that there are legitimate > reasons why the rDNS on a sending IP might not have an MX record, but no > really good reason why the actual domain in the From line in the envelope > would not have an MX record. > > So....is this some sort of a one-off DNS failure, a misunderstanding on my > part, a bug or none of the above? -- Dossy Shiobara | "He realized the fastest way to change do...@panoptic.com | is to laugh at your own folly -- then you http://panoptic.com/ | can let go and quickly move on." (p. 70) * WordPress * jQuery * MySQL * Security * Business Continuity * _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
