Uceprotect, a good guy or a bad guy?

August 13th, 2008 by bfebrian

There are some users reported to me that emails to certain domains are being rejected. After further check, I realized that the emails are being blocked by uceprotect.

This is the error message

—– Transcript of session follows —– … while talking to
some.domain.com.:
>>> DATA
<<< 554 5.7.1 Service unavailable; Client host [xxx.xxx.xxx.xxx]
blocked
using dnsbl-2.uceprotect.net; Net xxx.xxx.0.0/16 is UCEPROTECT-Level2 listed
because of 301 abusers. Your ISP xxx has to fix this. See:
httpx://www.uceprotect.net/rblcheck.php?ipr=xxx.xxx.xxx.xxx
554 5.0.0 Service unavailable
<<< 554 5.5.1 Error: no valid recipients

I heard about uceprotect before, how they block the entire ISP’s IP just because of some users of that ISP sending spam emails, but never though that will happen to me.

Normal rbl (dnsl) usually only block certain IP’s, but this uceprotect “smart” and “brave” enough to block the whole ISP’s IP range.

Simply said that I’m getting punished by uceprotect because somebody else spams. That is stupid.

I try so hard to make my IP’s clean, by removing viruses and make sure that no spam going outside through my mail servers. But my hard work is not enough, I still got blocked by uceprotect because somebody else spams.

Uceprotect in their website suggest that I should change ISP, that not that easy, and certainly not cheap.

So, I use a shortcut. I contact the admin of the domain that use uceprotect, and asked politely if it possible for them not to use uceprotect for emails from my domains. I gave them every information they need and explain my situations, and thankfully they agreed and approved my request.

Uceprotect may be want to be a good guy in spam fighter, but to me, uceprotect simply a bad guy.