Dirk,

It isn't necessarily < 1% of the original SPAM. 

Some spammers use a *known bouncer* to do their primary distribution - or
so it seems.

When I had '@ibm.net' later '@attglobal.net' accounts, it seemed that
their policy settings of delivering a copy of all bogus mail to *every*
user was a goldmine for spammers.  They cannot have been alone.

That's what happens when a bandwidth-provider, who gets paid while you
connect and retrieve all that crap, also runs a mail service....... and
according to ATT's CFO, it *was* part of ATT's biz plan to be paid for
such...

This is also why I wish more smtp implementations out there would do what
Sam has done with courier and provide for 'reject'ing incoming for
invalid/non-existent users instead of bouncing it. That isn't perfect, but
it does help reduce b/w use, time wasted, and storage on your server.

Good luck with it...

Bill Hacker


In <[EMAIL PROTECTED]>, on 03/23/03 
   at 10:40 AM, [EMAIL PROTECTED] said:

>Sam Varshavchik schrieb: 

>> [EMAIL PROTECTED] writes: 
>> 
>>> Hi there,
>>> i wonder if there is a way to block a set of addresses like  
>>> 
>>> [EMAIL PROTECTED]
>>> [EMAIL PROTECTED]
>>> [EMAIL PROTECTED]
>>> [EMAIL PROTECTED]  
>>> 
>>> with a "joejones*" style logic while still having a catchall address 
>>> (alias) for that domain.
>> 
>> Nope. 
>> 
>>> 
>>> background:
>>> The "joejones" adresses come from spam mail some A****** sent, giving 
>>> random adresses in our domain as return address. As i can't do anything 
>>> about the bounces (except for reporting the original spam to Spamcop or 
>>> Razor if i get my hands on it) i would like to simply drop those 
>>> messages.
>> 
>> Using one of the available blacklists of open proxies and mail relays 
>> should make this problem go away.  I highly recommend 
>> proxies.relays.monkeys.com; I can't think of any reason NOT to use it. 
>> 
>> 

>Hi Sam, 

>in fact i told Courier to use proxies.relays.monkeys.com and
>relays.ordb.org  and they work fine. The problem here is, that i don't
>receive relayed spam,  but its echoes. A spammer sends out his trash via
>whatever way and sets the  return path to a random address in my domain.
>So if one of the adresses to  which the original spam was sent is
>invalid, the mailserver in charge tries  to inform the sender (joejones -
>HAHA). These are the mails that come in  here. This will probably be < 1%
>of the original spam volume, but it is  annoying enough. 

>Regards 

>Dirk 

>==================================================
>Powered by SQWebmail


>-------------------------------------------------------
>This SF.net email is sponsored by:Crypto Challenge is now open!  Get
>cracking and register here for some mind boggling fun and  the chance of
>winning an Apple iPod:
>http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
>_______________________________________________
>courier-users mailing list
>[EMAIL PROTECTED]
>Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users


Regards,

Bill Hacker
-- 
-----------------------------------------------------------
[EMAIL PROTECTED]
William B. Hacker, III  FHKIoD
Managing Director  
Conducive Group (Asia) Limited    http://www.conducive.net
-----------------------------------------------------------



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to