Andrew Pounce wrote: > On Thu, Sep 06, 2007 at 09:22:02AM +0100, Kevin O'Rourke wrote:
>
>> 2007-09-05 15:28:12 1ISvrX-0000d0-Mx ** xxxx@???: Unrouteable address
>>
> Thats odd - I can connect quite well to the MX servers for yyyy.com - I suspect that there will be some problem within your own config.
> Sorry, yyyy.com was supposed to just be a dummy address, I was being a
little over-enthusiastic in removing identifiable adresses. The actual
problem was with opera.com. >> Could this be caused by some transient DNS problem? There doesn't seem
>> to be any other information in the logfile that I can use to trace the
>> cause of the error. This morning I tried the address using 'exim4 -bt
>> -v' and it seemed to resolve correctly.
>>
> That probably depends on your DNS servers - if they can't resolve the domain then they won't be able to route the message.
> DNS is resolving fine today and exim seems to be able to send mail to
that address now. So it was probably a DNS problem, we're on a
satellite internet connection which sometimes gets a bit congested.
However, I'd suggest that in cases like that maybe the error message
from exim (or in the logs) could be a bit more helpful?
