New DNSBL definitions

We have updated the default DNS Blacklist definitions in ORF. Compared to version 4.2, the following changes have been made:

  • ADDED: Barracuda Reputation Block List
  • ADDED: UCEPROTECT-Network Level 1
  • ADDED: UCEPROTECT-Network Level 2
  • ADDED: UCEPROTECT-Network Level 3
  • ADDED: Unsubscribe Blacklist (UBL) Resources
  • ADDED: SpamRats! Dyna List
  • ADDED: SpamRats! NoPtr List
  • ADDED: SpamRats! Spam List
  • ADDED: SpamRats! Combined List
  • REMOVED: All Spamhaus lists but Spamhaus ZEN
  • REMOVED: Blackholes.us lists
  • REMOVED: Spambag.org
  • REMOVED: Distributed Sender Boycott List (DSBL)

To get the new complete definition file, download blacklists-090416.xml. To get just the new blacklists, import blacklists-new-090416.xml. Please read the description of the new lists before enabling them.

Your feedback on the new lists are welcome.

OpenDNS & URIBL

If you are using OpenDNS and get DNS timeouts for the uribl.com Blacklist (UB-BLACK), that is because the administrators of URIBL decided to reject DNS requests from OpenDNS. The reason is that OpenDNS servers are alone responsible for 50 million DNS requests per day on the public mirrors of uribl.com. We recommend that you use your own DNS servers for ORF or if you are doing lookups in large volume (in case of uribl.com, 300.000 requests per day), set up a data feed. Alternatively, you can try getting OpenDNS to set up a data feed themselves.

Using your ISP DNS servers as DNS forwarders could also trigger a similar response from DNSBL/SURBL operators, because your lookups and everyone else’s on your ISP’s network add up.

For large volume lookups, please consider that the vast majority DNS blacklists and SURBLs are non-profit and run on donated hardware and bandwidth. Before using these, make sure to check their fair use policy and set up a data feed if necessary.

So What Will Happen Tomorrow?

The Conficker worm is widely regarded as the worst since SQLSlammer. It’s latest C variant will activate on April 1st, 2009, generate 50,000 domain names using an algorithm and pull its payload from one of these domains.

Estimations for the number of infected PCs range 9 to 15 million, which probably makes it the largest botnet ever, not even the Storm or the Kraken botnet come close in numbers.

My guess is it means more spam from tomorrow. A large botnet like this one can send several billions of spam a day, so getting the V1agr@ ads to your mailbox will be cheaper than ever.

I am sure you have already checked your network for infected PCs, now make sure that Spamhaus ZEN is enabled in ORF (will blacklist emails from botnet dial-up lines) and you have SURBLs on (will catch spam payload).

New Community Section: Feature Requests

We just launched a new community feature of vamsoft.com, the Feature Requests section. This is a community-powered feature request tracker that allows browsing, voting and submitting ORF feature requests.

In the tracker, you have 10 votes and it is up to you how you distribute your votes – let’s say you really want us to implement “Configuration Synchronization“, so you cast 6 of your votes on it and only 1 vote to “SCL Scoring“, because you consider it as just a nice-to-have feature. Of course, when “Configuration Synchronization” gets implemented, you get your 6 votes back (and anyway, you can change your mind anytime).

Visit the Feature Requests section at http://www.vamsoft.com/features

We are collecting feature requests since Day 1 and have recorded more than 150+ so far, but only the top requests were added to the tracker. This is intentional: what you might have needed two years ago may no longer what you want now. In any case, please feel free to submit your request via the tracker and convince others to vote.

Happy voting!

Exchange: Event ID 9667

In the recent months, we received multiple reports about MSExchangeIS 9967 event IDs in the Windows Event Log—our clients were wondering if ORF is involved in the issue. Well, it is not, but this Exchange 2007 problem is worth telling a few words about.

If you find warnings with event ID 9666 or errors with ID 9667, you are soon reaching/reached the quota on the number of Named Properties (you did not know you have anything called that, did you? :) The error message is something like this:

Failed to create a new named property for database “First Storage Group\Mailbox Store (server)”, because the number of named properties reached the quote limit (8250). User attempting to create the named property: “username“. Named property GUID: GUID. Named property name/id: “X-whatever“.

The issue is caused by the so-called X-headers. Emails have a well-defined set of standard headers, like From: which stores the sender or Subject: which stores the email subject. When email software wants to add something non-standard to the header, it adds them as X-headers, e.g. X-My-Special-Header: Is-Awesome.

Now, for every new X-header type seen, Exchange 2007 adds a new Named Property to the database, so X-My-Special-Header and X-Your-Special-Header take two entries, but X-My-Special-Header: Is-Cool and X-MySpecial-Header: Is-Awesome take only one, because they are of the same type, X-My-Special-Header.

Ok, but here comes trouble: there are awful lot of different software on the Internet and they simply love adding X-headers. The more the better. Given sufficient time and email traffic, you can actually reach the default quota of 8192 (or 16,384, but the max quota is 32,766). All those X-Spam-Status:, X-SpamInfo:, X-MIBTO:, X-Quarantine-ID:, X-DSPAM-Probability:, X-SEF-Processed:, X-LID:, X-My-Special: headers add up. I am subscribed to a newsletter where emails have a X-SEF-9ED26101-DDA5-4A4D-8030-449F502FF2BC header – even though this header is the same for every mailing, a quick search on the Internet shows that the GUID after X-SEF- varies, probably from installation to installation. Receive 8192 emails from various sites like that and you are out of luck. Sure, adding any X-headers is not wrong per se, it is just your Exchange that has hard time with these emails.

In case the quota is reached, Microsoft has solution on TechNet which basically recommends to set the quota higher and recover the database.

As a preventive measure, you can also remove unwanted X-headers— the HeaderFilterAgent does exactly that (disclaimer: we are not affiliated with the agent author). Before installing the agent, make sure that you have a good whitelist of X-headers you need: as can be seen in the comments, software sometimes relies on X-headers for communication.