The observant among you may have noticed that starting in Exchange 2007 Service Pack 1, Rollup 4, a new parameter debuted for Set-TransportConfig: DSNConversionMode. Those of you who like to experiment have probably already derived what it is that this Read More

EDIT: We updated this post on 12/9/2008 and corrected the step 4 below. I had a case earlier this month where the customer wanted a simple way to export the results of message tracking.  In the Exchange Management Console, he used the Message Tracking Read More

Exchange 2007 was the first release of Exchange to include Unified Messaging (UM) and this was the first time many of our customers started considering replacing their existing voice mail systems with UM. As with any new technology, many have sent in Read More

We're exploring making improvements to the experience of configuring Transport Rules. As part of this, we want to make sure we account for exactly how you are using Transport Rules today. The script linked to below will output some Transport Rules usage Read More

Many people use rules to automatically sort messages from various distribution lists into folders in order to keep the volume of email traffic in their inbox to a manageable level. This works for the most part - until someone decides to BCC a list. Read More

Recently I came across a situation where it was reported that Connection Filtering stopped working (IPs on the Blocklist and RBLs were no longer being blocked). The solution led me to write this blog to clarify some confusion about "when" connection Read More

EDIT 8/6/2008: Please see this post for additional information related to Hub throughput and different message sizes. Large message size: effect of transport database cache size on throughput. Background Recently one of our support engineers came to Read More

Summary Exchange 2007 SP1 has a default transport database cache size of 128MB. This size doesn't allow as much dynamic growth as may be necessary on Hub servers with higher than normal message rates, or when an unexpected load from increased message Read More

There are many scenarios in Exchange 2007 Server which requires parsing, monitoring, and analyzing Message Tracking logs. For example, in transaction log file and / or Database growth scenarios, Server got hit with spam messages, Looping message scenario, Read More

This is a second in my series of posts that deal with using Log Parser tool to analyze your Exchange 2007 transport logs. For the first post, please go here. I have written this blog post in a way that I walk you through building more and more complex Read More

Exchange Server 2007 uses new transport logs file formats that are easy to parse with one of our favorite Swiss Army knife tools, "Log Parser".  Log Parser (also referred to as LP in the rest of this blog post) is commonly used for analyzing Read More

At Tech Ed 2007 in Orlando, Florida, I was able to get some time with Charlie Chung, Senior Program Manager, to record a quick interview around some enhancements in the Edge Transport role and some other Transport related items in Exchange Server 2007 Read More

This blog post discusses Transport's use of the Temp Table folders during message processing (specifically during bifurcation) and mentions some common examples and scenarios in which Temp Tables gets used by Transport during bifurcation. Bifurcation Read More

Exchange Server 2003 supported a utility called WinRoute which allowed an administrator to connect to the Routing Engine Service on port 691, query it, and retrieve a view of the Routing Topology as seen by the server. The Routing Log Viewer in Exchange Read More

Email Journaling is the ability to record all email communication in an organization. In Exchange 2003, there are three different type of journaling: Message-only journaling Bcc Journaling Envelope Journaling. Envelope Journaling is the most suitable Read More