On Fri, 13 Jun 2003, Henrik Steffen wrote: > > > Hello Davide, > > unfortunately after the update to 1.16pre01 and reactivating > the CheckMailerDomain-feature our customers are crying again, > that they get the esmtp timeout. > > disabling CheckMailerDomain solves the problem for the moment, > but shouldn't this be fixed with 1.16pre01? > > >From looking at your code (SMTPUtils.cpp ll 2000-2020) I can > see that you have changed the order of the checks: First > the MX-Check, then - if MX-Check fails - the A-Check. > > Is it possible, that the MX-Check itself causes the timeout? > > We are running bind as nameserver for these domains on the > same machine, so there should not be such a timeout. > > Do you have any idea?
No. Last time I tried to send a message to one of those domains it went thru gracefully. The current check does the MX test first by leaving the A record check as last resort, so it basically does the same thing a normal MX resolution does. - 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]
