Re: Identifying the real problem

[mouss <mo...@ml.netoyen.net>]

  Le 17/09/2010 00:34, Karsten Bräckelmann a écrit :
> [snip]
>> I had in amavis-conf:
>>
>> $final_spam_destiny       = D_BOUNCE;
>> $final_banned_destiny     = D_BOUNCE;
>>
>> should be much better like this:
>>
>> $final_spam_destiny       = D_REJECT;
>> $final_banned_destiny     = D_REJECT;
>>
>> It was default with D_BOUNCE so i used this. But you are very right, the
>> bounce is old (according to the Postfixbook from heinlein) and i put reject
>> now. Thanks again!
> Thank you for fixing this. :)  One less backscatter source on the net.
>
>

not sure. if his amavisd runs after mail was queued (for example, if it 
was run as a content_filter in postfix), then D_REJECT will cause _his_ 
MTA to send a bounce, thus the backscatter.

So most probably, he is still a potential outscatter source.
Unless he is using amavisd-new to filter mail during the smtp 
transaction (with the remote/foreign client), which is uncommon, the 
only possible choices are pass, quarantine or discard.