Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've got a fresh install of Server 2008 R2 SP1, Exchange 2010 SP1, and Forefront 2010 Protection for Exchange. All on the same box, Exchange is CAS/Hub/MBS. This is a testing box, looking to evaluate the software configuration.

I've got it running, very default configuration. When I send an e-mail in with a bunch of known spam keywords it correctly delivers to Junk Mail. When I whitelist the sender/domain/IP (even all together) it still gets delivered to Junk Mail. Whilelisting by configuring in FPE -> Policy Mgmt -> Antispam Config -> Content Allow Lists or Filter Lists -> Allowed Sender List.

Mail headers show its being recognized as whitelisted, but still has the SCL score at 9:

X-MS-Exchange-Organization-SCL: 9
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Organization-Antispam-Report: MessageSecurityAntispamBypass
X-MS-Exchange-Organization-AVStamp-Mailbox: MSFTFF;1;0;0 0 0

Note the MessageSecurityAntispamBypass from being on the Allowed Sender List.

What do I need to change to get FPE/Exchange to deliver whitelisted e-mails to the Inbox?

share|improve this question
A workaround for the "problem" cited by EA: I created a hub transport rule, if an inbound e-mail has a SCL, remove the SCL header. Apparently this is an issue with the E2K3 bridgehead server setting a SCL and FPE blindly accepting it without regard for it's own filtering rules. – Chris S Aug 5 '11 at 19:01
up vote 2 down vote accepted

Looks like it might be a known issue:

You mentioned in chat that you're seeing the high SCL value set on messages that pass thru your E2K3 bridgehead but not on messages that deliver directly to E2K10 / FPE. If you're going to stay in production in that configuration then, obviously, you'll need to figure out why E2K3 is stamping that high SCL.

Sniffing the traffic between the boxes may be helpful (to assure that E2K3 is stamping the SCL before it's sent to E2K10) but the servers may "EHLO" each other and go into a proprietary binary data exchange-- I can't remember for sure. Changing the SMTP Virtual Server on the E2K3 side to use "HELO" only may help matters there.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.