Sam Varshavchik wrote :
cour...@thefreecat.org writes:
Digging in both syslogs I find :
Jun 25 17:39:59 miaou courieresmtp:
id=000086A8.467FD4F8.0000501D,from=<ca...@thefreecat.org>,addr=<ca...@thefreecat.org>:
Connection timed out
Jun 25 17:39:59 miaou courieresmtp:
id=000086A8.467FD4F8.0000501D,from=<ca...@thefreecat.org>,addr=<ca...@thefreecat.org>,status:
deferred
Jun 25 06:58:36 omallet courieresmtp:
id=00111F87.467BCC6C.00007332,from=<fo...@227.jp>,addr=<ca...@miaou.thefreecat.org>:
Connection timed out
Jun 25 06:58:36 omallet courieresmtp:
id=00111F87.467BCC6C.00007332,from=<fo...@227.jp>,addr=<ca...@miaou.thefreecat.org>,status:
deferred
Correct. A 456 error gets reported only after an earlier delivery
attempt to the recipient fails.
Do you mean I should be searching for a previous error ? Can you
direct me to the proper log files ? Or do I have to first activate
some diagnose switch somewhere ?
Then, Courier will reject all further
deliveries to the same recipient with either a 456 or a 556, dependening
on the circumstances, for some period of time.
This explains some of the delays I am experiencing (mail arriving between
a few hours and several days after being first submitted).
But that would mean the "link" between the two servers is working for some
time and then failing for some time (time out then error 456) and working
again (some mails arrive with a delay) etc. What could explain such a
behaviour ?
So this looks like a smtp problem but the link between omallet and miaou
*is* also smtp. And I don't have network errors.
Well, it is a network problem. The 456 is just the end result.
And why does the catchall (and omallet local posts to cat) work perfectly,
without delay, all the time ?
Ok. What should I be watching then ? Port 25 on both sides ? And look for
what ?
Thanks for your help,
5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Problem/Error 456...
