Exchange Server 2007 anti-spam myths revealed

In Microsoft CSS (Customer Service and Support) deal with many anti-spam questions. While anti-spam features that come out of box with Exchange 2007 provide a robust level of protection against unwanted garbage in your inbox, there’s still a lot of confusion out there as to how all parts work together. This post dispel some misconceptions […]

In Microsoft CSS (Customer Service and Support) deal with many anti-spam questions. While anti-spam features that come out of box with Exchange 2007 provide a robust level of protection against unwanted garbage in your inbox, there’s still a lot of confusion out there as to how all parts work together. This post dispel some misconceptions about E2007 AS features and reveals the top 6 SMTP anti-spam myths. Myth 1: Creating a hub transport rule to set SCL will affect behavior of SCLDeleteThreshold and SCLRejectThreshold. This myth applies particularly to case of Hub server role with anti-spam agents installed. While its fine to install anti-spam agents on a hub transport server, expecting that a hub transport rule with "set the spam confidence level to value" action’ll influence content filter delete/reject/quarantine is false.

Full Article: Exchange blog