ORF 4.3

In case you have missed the news: ORF 4.3 was released yesterday with a many improvements like DHA Protection or a new Honeypot Test. The complete list of changes is available in the ORF Change Log.

It should be noted that ORF 4.3 is an intermediate release, we spent the majority of development time with things that will be available in ORF 5 only, but I really cannot tell more at the moment-however, I am sure you will like ORF 5 more than any ORF release before.

ORF 4.3 Beta R2

The second ORF 4.3 Beta release is now available. It fixes all known bugs with 4.3 Beta R1. Get the new beta from

    http://www.vamsoft.com/beta/

UPDATE: Exchange: Event ID 9667

I just came across this post on the official Exchange team blog (not exactly fresh content, but I have a _huge_ backlog in my RSS reader) and I am happy to report that Microsoft has fixed the Event ID 9667 problem we blogged about earlier. The fix is available in Exchange 2007 SP1 Update Rollup 8.

Sadly, this does not help Exchange 2003 admins and I guess we cannot expect a similar fix for Exchange 2003 – its mainstream support has retired on April 19, 2009. Time to upgrade!

Publishing Honeypots

Now that the first beta of ORF 4.3 is coming really soon with Honeypot support, we have published an article about, well, publishing your honeypot email addresses. If you plan to use the new feature, you can start the preparations right now, it will take time for spammers to find your baits.

By the way, do not ever try to send to any of the following addresses: do not, write here. Unless you are an email address harvesting robot with intention to spam us occassionally, of course. Thanks!

ORF 4.2 and Exchange 2010 Beta

The first beta of Exchange Server 2010 became available a week ago and so we had a chance to test it with ORF 4.2.

The bad news: they are not compatible. The good news: they will be. Luckily, there are only a few changes in the 2010 Beta release that affect ORF, so once we found these changes and modified ORF 4.3, the initial tests ran successfully.

One reason why ORF 4.2 will not work is Exchange detection. We find local Exchange 2007 installations by checking various registry keys and these were changed in Exchange 2010 (actually, as the keys are versioned, it was expected). For instance, what was under HKLM\SOFTWARE\Microsoft\Exchange\v8.0 in Exchange 2007 is now under HKLM\SOFTWARE\Microsoft\ExchangeServer\v14\.

The other show-stopper is the name change of Exchange management PowerShell assembly – this was called Microsoft.Exchange.Management.PowerShell.Admin in Exchange 2007, now it is called Microsoft.Exchange.Management.PowerShell.E2010. Due to the name change, the ORF installer cannot install/uninstall the ORF Transport Agents or query their status.