Andréas Berg writes:
I've been looking at logs on both sides and I can find no reason for the 556 error. I get why the local delivery and the delivery from the second server fail as it could enter an infinite loop but the 556 I cannot understand.
The 556 error is generated as part of backscatter suppression. When Courier encounters a delivery failure for a specific email address, Courier stops accepting messages to the same recipient address for a short period of time.
The 556 error is the result of previous errors. In this case, as best as I can decipher your errors, you experienced a delivery failure to a specific address, so Courier stopped accepting email to that same address, for 1-2 hours. After the address expires, mail gets once again accepted for the given recipient address.
But, I think that backscatter suppression should not be activated for messages that get dropped into couriermlm. I that this needs a fix.
You can try this fix: change the command in .courier that invokes couriermlm from "| couriermlm msg [directory]" to "| couriermlm msg [directory] || exit 70". Similar change for .courier-default.
Also, the empty and the #@[] from addresses I see, is that intended or have we missed something in our configuration?
This is normal. It's one of the mechanisms that prevents endless bounce loops.
pgpnvpANSzB0n.pgp
Description: PGP signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
