We are making a move from Reddfish Listserver (horrible - don't even Google it) to Mailman. Reddfish "integrated" with Exchange by working with AD groups and contact types. During this migration, I have to get the current lists into mailman which means I have to get a nice clean list of line seperated email addresses to feed into Mailman. Here is the code I use to get this to work. Very simple, but I hope it still proves useful.

Have you ever had a tough time finding where an email address exists in your Exchange Org. Often times this comes from have a forward on a mailbox or a contact set to an external address. If you run the following in your Exchange Management Shell, you should be able to find almost any address or portion of address in your org. I like to format the output too, so you can change the | format-table part to however you would like the output to read.


get-recipient -filter {emailaddresses -like "Pattern goes here"}|format-table name,recipienttype,emailaddresses


Have you ever wondered how many mailboxes you have in your Exchange org? Well, if you have Exchange 2007 installed (not even any mailboxes migrated yet) you can fire up the Exchange Management Shell and throw down the following.

get-mailbox|measure-object


That simple!

If you read my earlier post about how I divided up my users in preparation for a mailbox migration to Exchange 2007, then you may be interested in the scripts attached. These are the scripts that I use to run batches of user migrations. It asks a couple of questions and away you go. Warning, use at your own risk.

Happy 2009 Everyone!

Here at work we have an automated system to create accounts based on data from our ERP system. We noticed after migrated many users to Exchange 2007 from Exchange 2003, that the newly migrated users could not send to users who had forwarded their accounts using UI to our account management system. The error complained of the contact having multiple primary SMTP addresses. Here's the little Powershell code snippet I ran to fix the issue.


foreach ($contact in get-mailcontact -resultsize unlimited){

For the past couple of months, one Exchange Server 2007 problem has plagued me. I had tried to install update rollup 3 in our organization. It worked fine on the front end servers, but certain services failed to start on the back ends. The Mail Submission, Mailbox Assistants, Replication Service, Search Indexer, and Service Host services all failed to "start in a timely manner." At that point, I punted and uninstalled the update.

I ran into an issue where Outlook 2007 on Windows XP on Exchange 2007 wouldn't autoconfigure and specifically didn't work with Outlook Anywhere. In my case, the mutual authenticaiton piece was failing. Thanks to this site for helping my diagnose the issue. The problem is with SAN certs. For mutual authentication to work with Outlook Anywhere, the FQDN for the external hostname used must match the Issued To field of the cert and doesn't work if you use an external hostname specified in the Subject Alternative Field.

We use Veritas NetBackup for system backup and recovery at work. The last step in our Exchange 2007 migration was to test backup and recovery of our mailbox databases. I was running what I thought would be simple tests to see if could restore the successfully backed up mailbox database. I was employing the Exchange 2007 recovery storage group (RSG) like a good boy and I was getting errors to the effect that I had not set up the RSG. After several failed attempts I had chalked this up to a Veritas bug and contacted Symantec.