Jeff Potter writes:
Hi List,What is the expected behavior for incoming email, when:1) The address is an alias, say, <URL:mailto:f...@domain.com>f...@domain.com, that expands to two local users, <URL:mailto:use...@domain.com>user- a...@domain.com and <URL:mailto:use...@domain.com>use...@domain.com2) <URL:mailto:use...@domain.com>use...@domain.com’s account is over-quotaWhat we’re seeing is a "456 Address temporarily unavailable” message to mail coming into the alias, meaning user-b doesn’t get the email, even though there account isn’t over quota.
The whole point of backscatter suppression is to prevent the mail queue from getting clogged up with mail to a nondeliverable recipient.
There's only one recipient address here, the alias address, and that's the only address that can be suppressed.
Extrapolate this to the condition where “<URL:mailto:f...@domain.com>f...@domain.com” is actually an alias for a few dozen people, and where on any given day one of them happens to be over- quota: it causes the entire alias to essentially constantly fail for everyone.
This means that aliases should either not include unreliable mail recipients, or backscatter suppression should be turned off (with all the repercussions that brings) in the bofh file:
opt BOFHSUPPRESSBACKSCATTER=none
pgpLR0WQahIVp.pgp
Description: PGP signature
------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
