What does “URIBL_BLOCKED” mean in the spamassassin log?
]
Answer #2
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
DNS-Blocklists often run on the “free for some” model and/or they may limit the number of queries you can perform to maximize resources.
If you were directed to this link from a rule description, then you have a DNS-Blocklist that is purposefully blocking your queries.
Resolving the block might be as simple as using your own non-forwarding caching nameserver to avoid being lumped together with other users queries; setting up your own mirror of the DNS-blocklist; or paying to use the blocklist. The choice is up to the DNS-Blocklist administrator.
http://www.uribl.com/about.shtml
For low volume end users, we provide public DNS mirrors distributed around the world to answer your queries through products like SpamAssassin which have built in support for URIBL.COM. Many other commercial anti-spam products support realtime DNS blacklists. Consult your documentation on how to configure your software to utilize multi.uribl.com for domain reputation.
For high volume users (see info on abuse http://www.uribl.com/about.shtml#abuse), we offer commerical Data Feed Services over RSYNC and DNS. Datafeed over RSYNC allows companies to run URIBL.COM data in-house, increasing speed and spam accuracy both. Datafeed service also provides extra datasets and prelist data that is not available in public DNS, improving spam accuracy even more! Datafeed over DNS provides the same great information over existing public DNS, without the need for setting up or maintaining your own hardware to download and serve the zone data.
Essentially, Site5’s requests to URIBL are exceeding their set limits for free public access, so URIBL is blocking requests from Site5. I don’t know if URIBL actually resets anything at midnight, but I’m hitting this error by 5AM Eastern time, so a midnight reset means that Site5 is burning through its available free URIBL requests very quickly.
I have submitted a ticket to request that Site5 look into a caching nameserver and/or URIBL’s datafeed service to allow SA to continue to use URIBL to keep the filtering accuracy up.
Answer this Question
You must be Logged In to post an Answer.
Not a member yet? Sign Up Now »
Answer #1
Hello,
I hope this reply finds you well!
URIBL is one of the DNS blacklists that SiteAdmin uses. It appears that the server you are on has hit the limit for the amount of emails it will filter on your particular server/account.
This should automatically correct itself at midnight and it should start working as expected then.
If for some reason it does not fix itself, or if you have any lingering problems, please feel free to open a ticket with our support department so that we can better assess the situation and help resolve the problem.
You can contact our support department by opening a ticket though Backstage or by emailing us directly at [email protected]
Thank you for bringing this issue to our attention.