Author: sam wun Date: To: exim-users Subject: Re: [exim] No route to host - but msg sent successfully
Leonardo Boselli wrote:
>I have found MANY incosistencies in the headers of your message.
>First that "at" has a rogue clock, (and probably sesame too) that does
>not allow to see the timing of the messge (I have received at 00:10:49
>UTC, (and I am absolutely sure, since the server is syncronized with
>two secondary time servers) while at say that has received from you at
>00:10:50.
>and sesame says that has received at 00:03:51 and delivered to the list
>
>at 00:04:02 ... you say you posted at 00:07:01 !!!!
>The most intesesting note is the X-Spam-Report that is included in the
>headers, could be this the reason that lead to problems, since messages are not
>delivered straight, but rather passed to some censorware ?
>Also the error messages show that sesame is unreacheable,
>but gives its IP6 address.
>Is possible that tries on IP6, print the message and then deliver ? can you look for other references to the same message in the loig ?
>
>
>
>
> Thanks for the trace. I put in anti-spam control with exim and there is
no IPV6 configured with the ethernet card in my gateway system.
That's why it caused that issue...
