jdow spake the following on 9/28/2005 1:55 PM:
> From: "Matthew Yette" <[EMAIL PROTECTED]>
>
>> On 9/27/05 5:22 PM, "jdow" <[EMAIL PROTECTED]> wrote:
>>
>>
>>>
>>> Please do not do this Matthew. It is a sign of VERY poor network
>>> management. It is also an excellent tool for spammers executing joe
>>> jobs. When I find myself joe jobbed the ISP that is bouncing goes into
>>> my procmailrc file with a redirect to /dev/null. I *NEVER* see anything
>>> from them again. People running real sendmail servers tend to place
>>> your address into their blacklists and drop all mails from your site.
>>>
>>> This is a feature that should be taken right out of SpamAssassin
>>> completely if it really bounces spam back to the "purported" (and
>>> virtually always forged) sender or postmaster.
>>>
>>> {O.O} Joanne said that rather more politely than she is thinking
>>> about it in her head. I've been joe jobbed this way. It is
>>> frustrating beyond belief.
>>>
>>>
>>
>> I understand your point of view completely - but I wouldn't call it poor
>> network management. It's a policy decision - and one that we deem
>> necessary.
>> We filter email for a lot of people - and the fact that we don't use a
>> quarantine system means that if something legitimate gets bounced, the
>> sender needs to know about it.
>
>
> So instead you facilitate joe jobs. Your network WILL get /dev/nulled
> on the first joe job I receive from it, you know. And I am not the only
> person who will do that.
>
> {^_^}
>
>
I would recommend only notifying the recipient, and let them contact the
sender. Makes less enemies in an already frustrated system.
--
/-----------------------\ |~~\_____/~~\__ |
| MailScanner; The best |___________ \N1____====== )-+
| protection on the net!| ~~~|/~~ |
\-----------------------/ ()
