Considering how bleeding edge the majority of my projects are I'm a little behind the curve on this one but I've finally managed to move all my Windows Servers across to Windows Server 2008. This includes the Domain Controllers, Web Servers and most critically the Exchange servers. This post is going to be cut into the following sections: Exchange 2007 Prerequisites on Windows Server 2008 Cross Forest Migration of Exchange 2007 Mailboxes and User Accounts Creating SSL Certificates for use with Exchange 2007 on Windows Server 2008 Exchange 2007 Prerequisites on Windows Server ...

A few weeks ago I 'inherited' a frontend anti-spam solution that was getting crushed under the weight of the Christmas run-up. Emails were taking up to a week to arrive at the back-end system and a lot of spam was getting through too. The solution consisted of two machines each with Dual Core 2.13Ghz Intel's, 2Gb of RAM & SATA disks behind a hardware load balancer. Unfortunately the combination of having to use swap due to the volume of incoming mail coupled with BackScatter attacks [the BackScatter attacks would of course require the original mail and the NDA to be written to disk for ...

First thing in the morning I like to have a quick browse through the Logwatch output for all my servers (or at the very least the ones I know are critical / the ones that have been giving me trouble) and for the most part the data is always quite concise and extremely useful. However there comes a point when erroneous activity makes your 15kb / 30kb Logwatch email start creeping up towards the 500kb / 700kb sort of size and usually its junk. The best way to sort this is by adding additional scripts/configuration to your standard Logwatch setup. I was finding that the main culprits were ...