zen.spamhaus.org problem today

C

chronic

Verified User
Joined
Dec 14, 2006
Messages
91
Am I the only one who had problems with rbl zen.spamhaus.org today? All received messages were bounced back from this rbl, I had to deactivate it in exim because I have been contacted by many customers about this problem.

Has anyone had the same problem and have any news about it?

Thank you
 
I've had issues with spamhaus several times in the past so I decided already several years ago to not use them anymore.
For example, various times they filtered mail because the customers home ip was (logically) in spamhaus, but the customer was sending via the server, not via his own home ip. But that home internet ip is always mentioned in the headers anyway as mail is created there. So Spamhaus was looking too deep.

I don't know what's up now, but this is the reason we don't use spamhaus anymore, too much false positives.
 
Thanks Richard, my problem is that since last night it has started refusing all incoming emails on the server for no apparent reason, I haven't done any updates or made any changes to the mail server and configurations.

Out of curiosity, I'd like to know what rbl you use, and maybe others too.
 
Yes I know your problem, maybe somebody else can enlighten if they encounter the same issue too since last night.

At this moment I'm using abuseat (would stop but is still working), spamcop and barracudacentral.
 
I think I have found the cause of my problem, maybe it will be useful to someone in the future, it was due to the nameservers in the /etc/resolve.conf file they were those of my server provider, which probably no longer resolved the rbl, changed those it solves correctly zen.spamhaus.org.
 
You can't use public open resolvers for Spamhaus. It's their policy, and they'll routinely screw you for doing it. It won't be consistent, so it'll look like a temporary issue, but it isn't.

Help for Spamhaus Public Mirror Users - Spamhaus Technology

Using Spamhaus' free legacy DNSBLs? Suddenly having issues with emails? Here's all the information you require to help fix the problem.
www.spamhaus.com www.spamhaus.com

Some implementations of the RBL will cause the result to show everything as blacklisted. A ton of cpanel and DA servers started acting like that in the last year. I personally started blocking outbound emails to servers that haven't been fixed to address this because I don't like them bouncing email back to my customers saying my IPs are blacklisted when it's their resolvers that were the problem.
 
Thanks for the clarification mxroute, but if I can't use public dns, what would be the correct solution to use zen.spamhaus.org?

Googling a bit, I ended up on this page https://www.intra2net.com/en/support/antispam/index.php which gives me a list of alternatives, but I don't know how reliable they are. In case I want to abandon the use of spamhaus which of these I could consider, does anyone adopt different lists than those proposed by default by the directadmin exim configuration file?
 
chronic said:
Thanks for the clarification mxroute, but if I can't use public dns, what would be the correct solution to use zen.spamhaus.org?

Googling a bit, I ended up on this page https://www.intra2net.com/en/support/antispam/index.php which gives me a list of alternatives, but I don't know how reliable they are. In case I want to abandon the use of spamhaus which of these I could consider, does anyone adopt different lists than those proposed by default by the directadmin exim configuration file?
Click to expand...

Sorry for the delayed reply. So you'd have to run private DNS servers that aren't recursive for the entire internet, or you'd have to pay spamhaus for a subscription which would allow you to use a custom URL for your RBL lookups, one which includes a key specific to your account.

I can hype mine at mxrbl.com, but I think it's better implemented as a SpamAssassin rule because removal requests are severely backlogged and this gives users the ability to override it. You can see how I've implemented it as an SA rule here: https://github.com/mxroute/da_server_updates/blob/master/spamassassin/local.cf
 
Also, from spamassassin config, you can set "dns_server" to use local resolve(127.0.0.1) or your own dns server to use with any RBL lookup api.
 
You must log in or register to reply here.
Back
Top