When you migrate or move your mailbox to Office 365 or to an on-premise Exchange Server 2010 server, you experience one or more of the following symptoms:
Junk E-Mail settings deployed by using Group Policy either fail to run or fail to take effect. These settings include Safe and Blocked Sender Lists and the Outlook Junk E-Mail filtering enabled/disabled setting.
When you use Outlook to add an email address to the Blocked or Safe Senders Lists, the address is either not displayed in the list or it is displayed in the list, but never synchronized to the Exchange mailbox.
Messages are unexpectedly marked as junk email.
Messages fail to be marked as junk email.
You notice differences between the Safe Senders List displayed in Outlook and Safe Senders as displayed in Outlook Web App (OWA).
Note This specific issue is present only after a mailbox is moved to an Exchange Server 2010 database. This should not be confused with other junk email issues.
The Junk Email rule is damaged or was generated incorrectly when migrated to an Exchange Server 2010 mailbox.
To resolve this issue, install the following update rollup before you move or migrate a mailbox:
2685289 Description of Update Rollup 3 for Exchange Server 2010 Service Pack 2
Note This update rollup will not resolve this issue if you apply the update after you move or migrate a mailbox.
To work around this issue, there are multiple options.
Use the MFCMAPI Editor tool to delete the Junk E-mail rule. Note this method may result in the loss of your original junk email settings.
Use OWA to add an entry to the Safe or Blocked Senders Lists. Then, start Outlook and either manually add an item to the Safe or Blocked Senders Lists or use Group Policy (GPO) to update the list. In some cases, you may have to start Outlook multiple times.
Add items to the Safe Senders List by using Exchange Powershell. Exchange Powershell commands can be used to append items to the Safe or Blocked Senders lists of multiple mailboxes in bulk.
For more information about how to use Exchange Powershell commands to add entries to the Safe or Blocked Senders lists, click the following article number to view the article in the Microsoft Knowledge Base:
2545137 How to configure the safe senders and blocked senders settings in Office 365
Note This article applies to both on-premise and Office 365 mailboxes. BPOS users should open a case with BPOS OPS.
Use a script to correct the junk email rules. A code sample of the script is available on the following Microsoft TechNet website:
For more information about a similar issue that occurs after you move or migrate a mailbox, click the following article number to view the article in the Microsoft Knowledge Base:
2695011 Junk Email settings do not work as expected after you migrate or move a mailbox to an Exchange Server 2010 SP1 Mailbox server
When the condition described in the "Symptoms" section occurs, when you use MFCMAPI to view the Junk E-mail rule, the Subject is missing. The following screen shot shows the Junk E-mail rule with the missing subject (PR_SUBJECT):
The PR_EXTENDED_RULE_CONDITION MAPI property contains both the Blocked and Safe Senders Lists.
You can compare what you see in the Outlook junk e-mail user interface (UI) against the Text string value of the earlierMAPI prop. This may help you determine whether the values that are shown in Outlook and those that were synchronized with the server are mismatched.
Additionally, some Safe and Blocked Senders information may be stored in the following registry key:
Microsoft Office Outlook 2007, Microsoft Outlook 2010, Microsoft Exchange Server 2010 Enterprise, Microsoft Exchange Server 2010 Standard, Microsoft Business Productivity Online Dedicated, Microsoft Exchange Online