If anyone out there is looking for a good guide to removing Exchange 2003 from your Exchange org, this four part guide is it. Thanks to Neil Hobson for writing it!

In my previous post, I mentioned I would post the source code for the script that I use to monitor the Exchange message tracking logs in an attempt to find hacked accounts. Attached to this post is the source code. In our environment I look for when the file grows to beyond a GB. At that point, the script will email me. This is run as a scheduled task (sorry, my coding skills don't allow me to make something that runs as a service) every 10 minutes. Enjoy!

One of my biggest gripes about Exchange 2003's Intelligent Message Filter was the inability to filter our own internal email senders' email. I found this article that explains how to let IMF check on authenticated sessions. I believe if I do this on the bridgehead server for my org, it will only filter things that leave the organization and will let our internal "spam" continue.

I have been working on figuring out how to move our 20,000 mailboxes to an Exchange 2007 environment. The following script is one of the first steps. This script goes through each mail-enabled user account and tags one of the extensionAttributes with a number 1-number of mail stores I will end up with.

I had the opportunity to write a quick script to query Active Directory for accounts that were forwarded and store those forwarded email addresses in a MySQL database to run a couple of reports against. This was pretty fun for me. I’ve attached the C# source code. I used the MySQL db driver located here.