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. 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.
There's no point in delivering mail to a recipient that's not receiving it.
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.
5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Problem/Error 456...
