Hi Steven
 
Thanks for your answer and sorry about TOFU - OWA is a pain ;-). 
 
Re: AGB - sure, but: If the service is *free*, the user shouldn't really complain 
about SMTP not being available. 
 
Re: Paying dial-up customers: I'm sure they appreciate the situation with SPAM and 
will not object too heavily about having to use a smart host to send mail. Believe it 
or not, even Exchange is able to send mail through a smart host ;-). And as soon as 
the traffic goes through your smart host, you can use your logs to absolutely 
positively identify spammers and enter their phone numbers in your black list - imo, 
maybe I'm oversimplyfying matters a bit here.
 
Re: abuse desk: ack, absolutely! And might I suggest:
 
case $spamhaven
   true
      if($noreaction && $contact_counter>1)
         spammer-isp-> blacklist
   false
      if($noreaction && $contact_counter>3)
          spammer-isp-> blacklist
esac
 
Sorry, I'm not a very good shell and/or perl programmer, more into the MS stuff ...
 
Regards
Fermin

________________________________

From: [EMAIL PROTECTED] on behalf of Steven Glogger
Sent: Thu 10/30/03 09:09
To: [EMAIL PROTECTED]
Subject: RE: [swinog] Mailempfang wegen SPAM blockiert / Mail receipt because of Spam 
blocks



hi fermin 

it depends on your AGB what the user is allowed to do and what not. 
i think that banning dynamic ip pool ranges (lets say via RBL dynablocker, 
etc.) is a temporarely solution to keep spam away. 
i know a lot of customers that use exchange servers and use isdn routers 
that connects each hour to the internet sending their emails and getting all 
the mails that are waiting for that company. but even then the customers 
should use their provider's SMTP server for the connection. 
but anyway, this doesnt keep the spammer away from configuring a smart-host 
entry to send his crap. 
i think that ISP should watch to their customers and react on abuse messages 
as fast as possible. 
if an ISP reacts on spam (what econophone didn't do) he will probably not be 
blacklistet as fast as possible in any RBL or other blacklists. well, this 
is the way at least i do. 
if ($noreaction && $contact_counter>3) 
        spammer-isp-> blacklist 
;-) 

-steven 

 

<<winmail.dat>>

Reply via email to