On 05/11/13 4:56 PM, Mark Goodge wrote:
On 05/11/2013 11:03, Jose Borges Ferreira wrote:
On Tue, Nov 5, 2013 at 4:43 AM, LuKreme <krem...@kreme.com> wrote:
Normally, bouncing undeliverable messages is the proper behavior
for a good netizen.
*NEVER* Bounce. Ever.
Reject, yes. Bounce? Absolutely never. If you bounce a message to
me, you get put on the deepest darkest shitlist imaginable where
you *never* get removed.
Your server, Your rules but don't try to influence people with bad
ideas.
Backscatter is done with bounces. Not all bounces are backscatter.
This.
The reason backscatter is a problem is because too many servers bounce
when they should reject. The solution to this is to reject when you
should reject, and ensure that you can reject in as many circumstances
as possible. It is not to reject even when you should bounce.
In practice, the number of occasions when an Internet-facing server
should bounce a message back to the public Internet is very low[1].
But it's precisely because it's an uncommon occurrence that it's
important to do it on the rare occasions that you need to.
[1] Bouncing back to an internal location is far more common, of
course, and pretty much essential if you are using an outbound edge
relay between your internal servers and the public Internet.
Mark
How do I configure postfix to drop the mail rather than reject? Is it
configurable? I have already configured my servers to REJECT all mails
not-intended to my domains and non-exsistant users and I do not accept
mails from non-exsistant domains. Is this enough?
What do I do when I accept an email, only to later find out the user's
quota is full? (it only recently that dovecot has an way for REJECTING
mail on such cases). Do I Bounce that email or drop the mail (After I
have accepted it? Surely, in this scenario the correct thing would be to
BOUNCE is it not?)?
I'm just trying to understand the ways to prevent BOUNCEs..
-Thanks
Vijay
