> But an address gets recorded there only when local *delivery* fails, > not when esmtpd rejects a message because of formal errors (sender > domain does not resolve, ...).
> Is it possible that you have some local delivery instructions that > terminate unexpected some times? You should look at your local > delivery process for that address, I think. Perhaps you can provide > som intformation about how this is organized. Something interesting > from "courierlocal" in your logs? OK, my bad. I left out some details. The machine on which the 456 error comes up has one of the MX records for the recipient domain, but it has no mailboxes. It forwards the mail to the server which has the mailboxes via esmtproutes. Now here is what I found in the meantime... If I do a telnet / smtp test from my PC to the mailbox server all is fine, mail gets through. If I do a telnet / smtp test from mx1 (the machine where error 456 comes up) to the mailbox server all is fine, mail gets through. If I do a telnet / smtp test from mx1 (the machine where error 456 comes up) to mx1 (localhost) all is fine, mail gets through to the mailbox server. If I do a telnet / smtp test from my PC to the mx1 server I get 456 - temporarily unavailable. This could mean that Courier does not know where to deliver the mail (as if it does not use esmtproutes), but then the test connecting from mx1 to mx1 (i. e. the very same courier) should also not succeed. Still clueless Dirk Kulmsee ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
