Matus UHLAR - fantomas wrote: > On 23.06.10 09:21, Bowie Bailey wrote: > >> I see the message "DNS lookup failed." in my logs for a particular >> email. When I test it, I get this: >> >> $ testmxlookup puertoislamujers.com >> Soft error. >> $ host puertoislamujers.com >> puertoislamujers.com has address 74.86.203.162 >> >> I thought that Courier would attempt delivery to the A record if there >> was no MX record? >> > > how do you know it has no MX records? The MX lookup didn't return valid > negative answer, it failed. It indicates DNS error. I can confirm this > - nameserver lookups for puertoislamujers.com timeout. > Their DNS is broken. >
Ok. I see. Kind of odd that their DNS returns an answer for A and fails for MX. >> I realize that the server at that address is not answering to port 25, >> but that should generate a timeout, not a DNS error. >> > > courier even does not try the A and it doesn't have to. > Because the MX query returned an error... I tested on one of my domains and verified that testmxlookup returns the A record when there is no MX with a properly functioning DNS server. -- Bowie ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
