Exchange 2007 anti-spam myths revealedFinally a blog post that makes these complex anti-spam configurations a bit more clear: In Microsoft CSS (Customer Service and Support) we deal with many anti-spam questions. While the anti-spam features that come out of the box with Exchange 2007 provide a robust level of protection against unwanted garbage in your inbox, there is still a lot of confusion out there as to how all the parts work together. The purpose of this post is to dispel some misconceptions about the E2007 AS features (where applicable differences introduced in Exchange 2010 will be pointed out as well). I present you the top 6 SMTP anti-spam myths - revealed! (drum roll) Myth 1: Creating a hub transport rule to set the SCL will affect the behavior of SCLDeleteThreshold and SCLRejectThreshold. Myth 1b: Setting an edge rule to inspect SCL value that the content filter sets will work out of the box. Myth 2: You need the CFA to move items to junk mail folder. Myth 2b: Setting the SCLJunkThreshold on the OrganizationConfig object from an Edge server will affect junk mail actions. Myth 3: Exchange/Outlook junk mail filtering is one single monolithic entity. Myth 3b: Running Set-OWAVirtualDirectory -JunkEmailEnabled $True/False will turn on/off the server side filtering. Myth 4: You need an Edge server to use safe list aggregation Myth 5: Putting a server IP on the InternalSMTPServers list of the TransportConfig object AND IP Allow List is a good idea. Myth 6: Running Enable-AntispamUpdates forces you to download all windows updates to your Exchange server. Continue at source for the full article: You Had Me At EHLO... Exchange anti-spam myths revealed
Send via e-mail | Submit to Digg | Add to Live Favorites
http://feeds.bink.nu/~r/binkdotnu/~3/Tw1lcTtwhdc/exchange-2007-anti-spam-myths-revealed.aspx
