Built For Designers & Developers

Is there a way to set up an email alias with a wildcard?

Google's GMail has a handy feature where you can use "[email protected]" as your email address. This allows for creating email aliases on the fly for use with questionable sources, for easily...

2 Answers In: Email By: InvisiBill [4 ]

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.

Thanks, that seemed to do the trick – I wasn’t thinking of the catchall account.

I disabled my catchall account several years ago due to the large amount of spam it was getting, so I’ve also added a filter rule at the end to fail any other messages that don’t trigger my wildcard rules, so that I don’t have to deal with the account filling up with junk.

If you send a failure, it will show the catchall account’s email address (“[email protected]” in your example) in the error message. For that reason, you may want to put some thought into the name of the account when you’re setting it up if you’re going to be sending bounces from it. I chose “invalid” for mine, so that it doesn’t look like a “real” address in the bounce message. I added this info as a comment on your KB article too.