• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 771
  • Last Modified:

Upgrade to Exchange 2007 and no email going to Junk Mail folder in Outlook

We recently upgraded to Exchange 2007 from 2003.  Most of our clients are using Outlook 2003.  We also are  using Postini as a spam filter.  Before the upgrade, users would often received legimate mail into their junk email folder, and I could never find a way to turn this off.

After upgrading to Exchange 2007, no users have any mail going into their junk mail folder, so now they're convinced something is wrong and that they are missing important emails that are lost somewhere.

Does anyone have any information on this? It's starting to get the attention of senior management too.

2 Solutions
It is almost impossible to prove a negative. There are only two ways that content gets in to the junk email folder - Outlook's own filtering and IMF. IMF isn't even installed by default on Exchange 2007.
It isn't clear what you want. Do you want some email to go in to the junk email folder?

You have to use the Exchange Management Shell (CLI) to create a policy for the Junk Mail Folder. This is the only way i know how to do it, not to say it's the ONLY way.
See   http://exchangepedia.com/blog/2007/02/exchange-2007-content-filter-how-to_07.html

"So where's the equivalent of IMF's Store threshold? (to move messages to users' Junk Mail folders)?

It's called SCLJunkThreshold, and it resides in a different location - in the Organization configuration. It can be set using the set-OrganizationConfig command:
set-OrganizationConfig -SCLJunkThreshold 5
Setting SCLJunkThreshold not intuitive?

Before you jump to conclusions about this being counter-intuitive, or confusing - which it may be, consider this - it is in response to the different server roles in Exchange Server 2007.

The gateway actions - delete, reject and quarantine - can be thought of as message transport actions, and thus applicable to transport server roles (the Edge server, or the Hub if you have antispam agents enabled on it). Moving messages to users' Junk Mail folders can be thought of as something that happens at the Store, performed by the Mailbox Server role.Another aspect to consider when setting the SCLJunkThreshold - if you're in a topology with an Edge server, the SCLJunkThreshold on the Edge doesn't impact anything. This needs to be set on your Exchange Org - the Edge server is not a part of it.

The Defaults: By default, the SCLJunkThreshold is set to 4. If you have an existing Exchange Server 2003 SP2 server installed, and you haven't tweaked the Store threshold, IMF v2's default Store threshold of 8 is used - this is what you'll see in the Org's SCLJunkThreshold. Given that the SCLRejectThreshold is set to 7 by default, messages will not move to users' Junk Mail folder unless the SCLJunkThreshold is lower than the transport thresholds (i.e. the Delete, Reject and Quarantine thresholds).

How the Junk Mail threshold is calculated: Unlike the transport actions of deleting, rejecting, and quarantining messages - which check for SCL equal to or higher than their respective thresholds, for moving messages to Junk Mail folder the Store checks for SCLs higher than the SCLJunkThreshold. This is consistent with the behavior of IMF in Exchange Server 2003 (read previous post: IMF Confusion - Store threshold rating text in UI).

If you want to disable rejection of messages with SCL of 7 or above, use the following command:
set-ContentFilterConfig -SCLRejectEnabled:$false"

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now