Re[2]: What's this? Spam filter testing?

[Robert Menschel <Ro...@Menschel.net>]

Hello Kai,

Monday, April 26, 2004, 3:31:29 AM, you wrote:

KS> Heinz Ulrich Stille wrote on Mon, 26 Apr 2004 02:10:40 +0200:

>> But I don't want to tell a spammer anything, so I want to scan for spam
>> before bouncing.

KS> You don't want to check mail for non-existent users for spam, you
KS> want to reject it right-away, because the user doesn't exist - unless
KS> you are a masochist or run a honeypot ;-)

Or a retail business that doesn't want to lose any customers because of a
misspelled email address (such as serrvice@ instead of service@). We
accept any/all @ourdomain emails, and let SpamAssassin file away the
spam, and then redirect the non-spam to someone who can figure out where
it was supposed to go.

Bob Menschel

Re: What's this? Spam filter testing?

[Kai Schaetzl <ma...@conactive.com>]

Robert Menschel wrote on Mon, 26 Apr 2004 21:37:39 -0700:

> Or a retail business that doesn't want to lose any customers because of a
> misspelled email address
>

Sure, if there's a need you use a wildcard. We allow wildcards for all of 
our customers, but do not use one of our own. What I wanted to say in my 
posting is that it doesn't make much sense to first test the mail for spam 
and *then* reject it because the address doesn't exist as the OP does. Of 
course, there are gateway setups where it doesn't work any other. But with 
most mail systems one should still be able to extract the addresses/users 
from the backend and put them on the gateway as well, so that the gateway 
knows about them.


Kai

-- 

Kai Sch�tzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.de & http://msie.winware.org