Organization: W S Rupprecht Computer Consulting, Fremont CA
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (berkeley-unix)
Cancel-Lock: sha1:uJ5Cmf9Granuzya8o4vN/lH4+3c=
Date: Sun, 29 Feb 2004 15:01:49 -0800
In-Reply-To: <20040229212941.GH22426@uriel.eclipsed.net> (gabriel
 rosenkoetter's message of "29 Feb 2004 21:29:41 GMT")
Message-ID: <x78yilxzfm.fsf@capsicum.wsrcc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: current-users-owner@NetBSD.org


<#secure method=pgpmime mode=sign>
gr@eclipsed.net (gabriel rosenkoetter) writes:
> On Thu, Feb 26, 2004 at 10:58:12PM +0100, Florian St?hr wrote:
>> Well, I was kicked off the mailing list because my mailserver refused lots
>> of spam coming from the current-users list.
>
> While it would be nice if this didn't cause unsubscriptions, you
> really shouldn't ever bounce spam. It doesn't do any good: the
> envelope sender isn't responsible for someone forging their email
> address, if it's even a valid email address. Just drop it on the
> floor instead.

It doesn't only happen with bounces.  It happens when one *rejects*
spam with a 550.

IMHO quietly dropping messages is the wrong thing to do.  One should
always reject them at the SMTP level so that the sender (if they are
legit) will find out about the rejection.  In the case of directly
delivered spam, the sender will just quietly go onto the next message.
They certainly aren't going to bother sending a bounce to the sender
address they just forged.  That would just get them whacked.

-wolfgang