A dodgy spam definition update from Cloudmark has crashed users' email clients. Users of the anti-spam service were left unable to run either Outlook or Outlook Express without their email clients crashing. Cloudmark blamed the problem on a corrupted file that formed part of the update, issued on Thursday. The firm has now …
M$ helped for free!
After struggling with this problem a quick call to MSFT tech support resulted in them dialling in to fix the problem for free! They must have been bored. Did the cloudmark update for us and all. Nice.
Hmm. I enjoy quite good results with Vipul's Razor, although to be fair it does occasionally trash a DSN or three (could be explained by an included spam attached as part of the report). I let Vipul'z Razor (which uses the cloudmark network and was clearly not affected by this issue - it's written in perl, BTW) have first go at incoming mail, and if not classified as spam at once let my bayesian filters go at it, otherwise (spamtrap or no) the mail just gets filed away as almost-certain spam and has the benefit of costing almost no disk I/O. This assumes it got past my SMTP-level defenses, of course. A spamtrap classifies mail as spam and submits to Razor as spam automatically, while a human-assisted process submits most bayesian-classified remaining spam to Razor. The effect is that most mails get noted as spam right away with a low enough false positive rate that I can check quite infrequently, and I can count and check the remaining classified spam myself daily as there's not too much of it for verification with a much greater confidence in accuracy (my database is quite large). Most of the spam actually comes from forwarders, of course, since spambots are mostly caught at the SMTP stage. This includes easy-to-fingerprint 419 scams and such sent from ISP nets and freemails. Oh, and there's near-zero spam in my inbox with no possibility of any mail actually getting lost and a much greater possibility that I will lose patience getting complacent about how damned good my results are and just throwing my spam folders away. Which is all very pleasant. :-)
What do false positives have to do with the issue at hand? It seems like Cloudmark was crashing Outlook, not producing falses (negatives, positives, who cares?).
I just did a Compaq System Recovery trying to get Outlook going, unaware of this issue.
I now know more about Outlook problems than any normal human should (except the MVP of Outlook Development at Microsoft). At least they coulda sent me an email telling me about it!
Wait, never mind, my email WASN'T WORKING at the time.
That's all you need to know, really.
Yes, in fact, it was a false positive. It declared ALL messages, sent and received, to be spam, and thus removed your access to them. Granted, that meant taking out outlook, which is a rather unorthodox technique.
- Tricked by satire? Get all your news from Facebook? You're in luck, dummy
- Feature TV transport tech, part 1: From server to sofa at the touch of a button
- Google straps on Jetpac: An app to find hipsters, women in foreign cities
- Updated Microsoft Azure goes TITSUP (Total Inability To Support Usual Performance)
- The Return of BSOD: Does ANYONE trust Microsoft patches?