Posted by & filed under Exchange Server.

Looks like Spamhaus SBL+XBL has become Spamhaus Zen.

I have already switched my spam filter over to the new list and I must say, it is much more effective. Before I was averaging 19%-22% spam from Spamhaus SBL+XBL, and with Zen I am getting 29% spam rate, with only a few minor false positives. Spamhaus SBL+XBL will be discontinued soon, so I’d switch over immediately.

Posted by & filed under Exchange Server, Windows / Server.

In my relentless efforts to squash the ever increasing spam problem within our organization, I have added ORF Enterprise Anti-Spam by Vamsoft to our anti-spam arsenal.

ORF is not meant for Exchange Server only, it binds to any SMTP server and filters before/after arrival of messages. It seems any Exchange Server specific anti-spam product is much more expensive than it has to be. Perhaps it is because the cost of Exchange Server implies the owner has the money to buy an expensive anti-spam product? Maybe.

To the side are the stats from a typical day. 68% of all email received and tested is spam. By far the most effective feature is the DNS blacklist.

Name Spam %
SpamCop 18%
CBL Composite Blocking List 29%
Spamhaus SBL+XBL (Combined) 19%
Distributed Server Boycott List (Single) 4% China and Korea combined networks 6%
Not Just Another Bogus List (NJABL) 18%
Open Relay Database < 1%
SORBS Combined List 25%
Abusive Host Blocking List (AHBL) 2%
Spamhaus SBL (Spam Block List) 1% Korea network 5%
FiveTen Blackhole List 30% China network 6%
Spamhaus XBL (Exploits Block List) 25%
Passive Spam Block List 21% 3%
No-more-funn 28%
Blitzed Open Proxy Monitor List Combined 1%

Posted by & filed under Internet Information Server, PHP.

To all those (3 people) who need to use file_get_contents in PHP on IIS 6, you may notice it doesn’t work by default. To see if it works, place the following code into a file called test.php.

echo $content;

You should have the first 20 bytes of the google source code echoed back to you on the page when it is executed. If not, you may need to play with IIS 6.

Does fsockopen work?

IIS 6 by default does not allow sockets to be created on port 80 (file_get_contents works on this port, of course). This is a result of how IIS 6 accepts connections. To get file_get_contents to work, you need to enable IIS 5 Compatibility (Isolation Mode) on IIS 6. You then need to choose Low (IIS Process) under “Application Protection.” Isolation mode settings are found in the IIS Admin Interface –> Right-click on Web Sites folder and look under the Service Tab.