On Wed, 18 Apr 2007, Davide Libenzi wrote: > On Wed, 18 Apr 2007, John Kielkopf wrote: > > > > > > so it is easier > > > that temporary network problems end up being hidden by its caching. > > > > > > > > > > > > - Davide > > > > > > > > But why should a temporary network problem cause any issue in the first > > place, unless that problem is a bad DNS entry? Network connectivity > > issues during a DNS query should at most cause a delay in sending the > > mail, but the mail should eventually get through without user intervention. > > > > I'm still concerned that your fall back to "A" after MX timeout could > > cause a permanent delivery failure (trying to send to the host pointed > > to by the "A" record, potentially hitting an SMTP server that would > > refuse the delivery) when the failure should only be temporary (can't > > get any results from the domain's DNS servers due to a network failure > > somewhere while trying to lookup the MX record). Admittedly, this would > > be a _very_ small window of opportunity, but still possible if Xmail > > handles this as you suggest. > > That can be done. Anyone has a domain name with no MX handy, for me to > test?
Never mind, found it (example.com :) Now I see XMail going to A-record when sending to example.com, that is right. Now I need to test the other part, that is a temporary remote DNS error ... - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
