Index: [Article Count Order] [Thread]

Date:  Tue, 17 Feb 2009 12:28:15 -0800 (PST)
From:  Dan Kriwitsky <webhosting (at mark) yahoo.com>
Subject:  [coba-e:15099] Re: Spam Problem
To:  coba-e (at mark) bluequartz.org
Message-Id:  <35101.43898.qm (at mark) web65614.mail.ac4.yahoo.com>
In-Reply-To:  <200902172052.n1HKqK22028981 (at mark) ana.xnet.com.mx>
X-Mail-Count: 15099




--- On Tue, 2/17/09, Rodrigo Ordonez Licona <rodrigo (at mark) xnet.com.mx> wrote:

> The semi-solution  (I would call it an aspirin) is to
> remove your own
> addresses and domain names from the whitelist,

Ah, you're running SpamAssassin? 

> 
>  in which case will trap incoming spam, 
> 
> but the email would have been received anyhow 

Only blocking during SMTP stops the mail from being received. DNSBL are good for that.


> DNS BL are not very useful in my case I actually used them
> to no avail, I
> tried to block ISPs Ip adresses blocks from the offending
> spammers however
> their IP/server database seemed to be unlimited (3 weeks of
> daily blocking
> new ip ranges and domains-- "maybe try harder is the
> suggestion for now" ),
> and spam from different regions of the world, from valid
> companies and valid
> hosting providers kept coming in.

I guess it depends on what DNSBL you use. Run some of the IP's past http://www.dnsbl.info/dnsbl-database-check.php and see if there might be a better DNSBL that is catching these spammers before they hit you.


> So its spamassassin's call now, (the cost on our cpu
> cycles for now.)

It's pretty impossible not to receive no spam unless you just unplug the server. Spam is a fact of life.


-- 
Dan Kriwitsky