>> You can only purge them automaticly, I'm not sure that's to smart.
>> The best is to reject based on envelope sender or recipient,
>> that way you can tell the "offening" server that you rejected the message.
>> (This is done throug the files control/badmailfrom and control/badrcptto.)
>
> badrcptto might help, together with some heurestics.
> (There were way-too-many forms of [EMAIL PROTECTED])
> goodrcptto might help better :-)

For now I recommend putting all known forged addresses in badrcptto,
this is the only "easy" way to avoid any high volum traffic over a 64kbps line.


>> BTW: would it be possible to see one COMPLETE
>>      bounce message you are having trouble with.
>
> I have stored about five thousand of them.
> The basic pattern is simple:
> Some faked Received line, then someone at saturn.bbn.com (a DSL? dial-up?),
> then some open relay in .cn, .jp or .kr domains
> (I have seen quite a few of them) and then the recipient,
> bouncing the message back.
> I can post one of the messages, but which one?
> Don't want to be unfair to the remaining open relays :-)

Block them with ORBS ;D


> A few people suggested to sue the spammer for misusing antek.cz's name.
> Can anyone suggest how?

Not me, but I'm sure you can get a lawyer to help you with this.


MVH André Paulsberg


Reply via email to