Junk store threshold not configured
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at https://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2010-04-28
The Microsoft Exchange Best Practices Analyzer queries the Exchange environment for the presence of Exchange Server 2007 Hub Transport or Mailbox server roles.
If Exchange Analyzer finds either Exchange Server 2007 Hub Transport or Mailbox server roles, the tool executes the Get-OrganizationConfig cmdlet to query for the value of the SCLJunkThreshold parameter for the Exchange organization.
The Analyzer tool queries the Exchange environment for the presence of Exchange Server 2010. If Exchange Analyzer finds Exchange Server 2010, the tool executes the Get-OrganizationConfig cmdlet to query for the value of the SCLJunkThreshold parameter for the Exchange organization.
The SCLJunkThreshold parameter for an organization specifies the Spam Confidence Level (SCL) at which a message is moved to the Junk E-mail folder.
If the Analyzer tool determines that the SCLJunkThreshold parameter for an organization is set to the default value of 8 in Exchange Server 2007, Analyzer generates the following best practices message:
Junk Store threshold is currently configured to move messages to recipient's Junk folder when they have a Spam Confidence Level (SCL) value of 8 This is the default value for the Junk Store threshold. However, the recommended value is 4. You can configure SCL thresholds by using the Set-ContentFilterConfig cmdlet in the Exchange Management Shell |
In Exchange Server 2010, the Analyzer tool generates a best practices message if the value of the SCLJunkThreshold parameter is not 4.
This message indicates that the SCL threshold for moving messages to the Junk E-mail folder may be set too high. The default SCL level is intended to minimize the number of legitimate e-mail messages that get routed to a user's Junk E-mail folder. However, when the default SCL is used, more unsolicited commercial e-mail (UCE), also known as spam, is sent to a user's Inbox folder. The recommended value for the SCLJunkThreshold parameter is 4.
To address this issue, use the Set-OrganizationConfig cmdlet in the Exchange Management Shell to set the value of the SCLJunkThreshold parameter to 4.
To set the value of the SCLJunkThreshold parameter to 4 using the Set-OrganizationConfig cmdlet
Use a Set-OrganizationConfig command that resembles the following:
Set-OrganizationConfig -SCLJunkThreshold 4
For More Information
For more information about how to configure content filtering, see the following topics:
"Enable or Disable Content Filtering"
(https://go.microsoft.com/fwlink/?LinkId=145158)"How to Enable and Configure the Spam Confidence Level Thresholds"
(https://go.microsoft.com/fwlink/?linkid=96099)"Set-ContentFilterConfig"
(https://go.microsoft.com/fwlink/?LinkId=145161)