Hi. On Monday 18 February 2008, Dirk Kulmsee wrote: > It cannot be true that Courier blocks legitimate mail because of errors > that happened earlier. But I am lost here. I don't find an error in my > configuration. I did not find much info on this problem. Could someone give > a description when error 456 is triggered, what time values are behind > "temporarily unavailable", which settings to look at?
Courier has a list of local addresses that triggered errors in the past. Mail to those addresses gets rejected for some time going to prevent local overload. This is not really a problem I think. 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? And additionally as always on this list: If you want real answers, please provide real data. "recipient.domain" is no good idea. AFAICS the recipient just gets a bunch of spam, so it shouldn't matter. :) regards, Bernd -- Press <CTRL>-<ALT>-<DEL> to continue...
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- 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
