Having read quite a few of the messages in this list about bounces, I really didn't find any (though they may be there) related to preventing bounces for resource limits, and other unpredictable and strange occurrences. That is my question, NOT bad recipient, etc. Yes, I know bounces and rejects are totally different.
The first thing that came up lately was an error in configuration I made when creating some spam training transports. Message was sent, accepted, and, then bounced when a backend error occurred. Starting poking around for Postfix exploits as well, and, noticed the Delivered To header exploit that created bounces apparently. So, certainly for exploits, I'd hate to generate bounces that go to un-intended victims, but, you can't predict those I suppose. So, that is the reasoning I have. So, based on these reasons, is there any good way to never send any bounces from Postfix? Soft-bounces seems to work, but, I've seen posts that say never leave it this way and of course it keeps them all in the queue but maybe that's good. Others have said to comment out the bounce server, but, then replies say it's there for good reason (not sure what that is though in modern times). My intent here it to not be accused of sending backscatter and thus spam of course, and, especially with exploits, this is a possibility I'd like to avoid if possible. Nothing more or less. So, how do others handle this? Or, do you just handle when it occurs and not worry about it? Steve
