Manage Learn to apply best practices and optimize your operations.

Controlling spam in Exchange 2007 at the edge transport server level

While having an effective antispam and antivirus plan is critical in Exchange organizations, improperly configuring it can cancel out even the best product. Whether you're planning to use hosted filtering or protecting user mailboxes locally, there's always more to learn about keeping your Exchange shop secure.

Having an effective antispam and antivirus solution in place in your Exchange Server organization is critical. How you fit these solutions into your Exchange architecture is nearly as important as using the right product.

Since spam reportedly accounts for 90% of all inbound email, it's best to keep it out of users' mailboxes. What's the best way to do that? Ultimately, the best approach is to use hosted filtering.

Hosted filtering points your MX DNS record to a third-party filtering provider that removes spam and sends remaining messages to the Exchange organization. This ensures that Internet bandwidth isn't wasted on spam and that viruses never reach your organization.

While this approach works well, many organizations prefer to deal with spam and viruses locally. In these situations, the best approach is to eliminate spam and viruses at the edge transport server level. Microsoft states that the edge transport server's primary function is spam control. Even so, there are other reasons to eliminate spam and viruses at the edge transport server level.

Exchange Server 2007 uses a centralized hub transport. Every message passes through the hub transport pipeline, regardless of whether the message was sent from the Internet or from an internal user. If you attempt to eliminate spam at the hub transport server level -- or even at the mailbox server or mail client level -- spam will reach the transport pipeline before it's eliminated.

If 90% of all messages are spam and you allow it to reach the transport pipeline, then your hub transport server must process about 10 times more mail than usual. This can back up message queues and affect server performance.

Many small- and medium-sized organizations choose to piggyback the Hub Transport Server role onto their mailbox servers. In these cases, the server's resources may be stretched thin before even throwing spam into the mix.

Additionally, some organizations may be required by law to archive all email messages. Because most message archiving products copy messages as they flow through the hub transport, allowing spam to reach the hub transport pipeline increases archive storage costs. It may also make it more difficult to locate specific messages within the archives, which are congested with spam.

Spam is a nuisance, but viruses are harmful. I recommend scanning for viruses at the edge transport server level. You should also have Exchange-aware antivirus software installed on all mail servers. Finally, be sure that you have antivirus software installed on client machines as well as the appropriate Outlook plug-in.

About the author: Brien M. Posey, MCSE, is a five-time recipient of Microsoft's Most Valuable Professional (MVP) award for his work with Exchange Server, Windows Server, Internet Information Services (IIS), and File Systems and Storage. Brien has served as CIO for a nationwide chain of hospitals and was once responsible for the Department of Information Management at Fort Knox. As a freelance technical writer, Brien has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies. You can visit Brien's personal website at

Do you have comments on this tip? Let us know.

Please let others know how useful this tip was via the rating scale below. Do you know a helpful Exchange Server, Microsoft Outlook or SharePoint tip, timesaver or workaround? Email the editors to talk about writing for 

Dig Deeper on Exchange Server setup and troubleshooting

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

If your exchange database is attacked by viruses, then there is a bright change that your edb files will get corrupt/damaged and will become inaccessible. So, in such cases you can use Exchange inbuilt utility Esutil which can repair your corrupt or damaged edb files but if the edb files are severely corrupt or damaged due to virus attack, then Esutil won't work and then, you can take the help of any third party repair tool. One such most trusted Exchange repair tool is Stellar Phoenix Mailbox Exchange Recovery, which is a powerful Exchange repair utility that helps in restoring the inaccessible user mailboxes by repairing the damaged edb files easily and quickly.
Use Exchange hosted filtering. Exchange hosted filtering is a service that incorporates multiple filters to actively help protect businesses' inbound and outbound e-mail from spam, viruses, phishing scams, and e-mail policy violations. It can ensure that Internet bandwidth isn't wasted on spam and that viruses never reach your organization eliminate spam and viruses at the edge transport server level