Try the below link out and see if it resolve your problem. http://answers.microsoft.com/en-us/office/forum/office_2010-outlook/exchange-junk-mail-configuration-not-functioning/485f7dbb-8988-4911-9029-055eecbae3f1?tab=MoreHelp Girishp

We're using Exchange 2010 SP1 RU4, and I have a user who has managed somehow to get a very corrupt TrustedSendersAndDomains list in her junk mail configuration. Somehow: She's managed to get 3590 entries in the list, although the limit is 1024She has several entries in the form 'user@domain' (including the single quotes). Outlook and OWA both refuse to allow changes to the list because the quoted addresses are invalid. Using EWS as an admin, I can't remove a quoted entry because I have to give an exact string, including the quotes, and PS detects it's an invalid address Even worse, I can't discard the list. If I do: Set-MailboxJunkEmailConfiguration identity -TrustedSendersAndDomains $null I get back Junk e-mail validation error. Value: 'user@domain'. + CategoryInfo : NotSpecified: (0:Int32) [Set-MailboxJunkEmailConfiguration], JunkEmailValidationException + FullyQualifiedErrorId : B928B6E0,Microsoft.Exchange.Management.StoreTasks.SetMailboxJunkEmailConfiguration Worse yet, every PowerShell command to change any aspect of the configuration gets this error. So it looks like I have corrupt entries in the list that I can't remove because the list contains corrupt entries. Do I have any way out of this impasse? Thanks Alan

why cant you move the mailbox and give a try. while moving mention more number of corrupted items. Kottees : My Blog : Please mark it as an answer if it really helps you.

Hi Any update on this thread, perhaps you could also try the solution on the below thread http://social.technet.microsoft.com/Forums/en-IN/exchangesvradmin/thread/8fa6f5dd-9b7d-4df3-b0bb-1d6fe43e014b Cheers Zi FengZi Feng TechNet Community Support

Thanks for the help so far, all. Using MFCMAPI to delete the Junk E-Mail rule from the mailbox seems the most promising solution (there's no actual answer posted in many of the links provided). I've done some testing and learned some interesting things, but not quite succeeded. So: using a test system (!) I can set up a mailbox and put some safe senders into the Junk Mial rule with Outlook. Using MFCMAPI I look in the Associated Contents Table for INBOX, and there's a rule with PR_SUBJECT="Junk E-Mail Rule". Inside that rule the safe sender and blocked sender lists are in the property PR_EXTENDED_RULE_MSG_CONDITION. This is a binary property, and it looks consistent with being a dump of a hashtable that I've seen documented. It contains the addresses I've added to the safe sender list; and from my live system it also contains the entries we pushed with a GPO (these don't appear in Outlook or in OWA so are obviously marked somewhere) So, we know how it all fits together and how the Exchange 2010 aggregation works, I think. Now to clearing up. With no Outlook client running I use MFCMAPI to delete the rule, selecting an unrecoverable delete operation. But: I restart Outlook (in online mode, not cached mode) and the junk mail settings are still there. And as soon as Outlook is running, the safe sender list aggregation pushes the rule back into the mailbox and I'm back where I started. So, it looks like in order to clear all this corruption I have to Stop every Outlook client connected to the mailbox (it's a shared mailbox, so more than one, but manageable)Delete the rule from the mailboxClear up some cached data from every Outlook install Now where is the cached data being held on the client systems?? UPDATE Just after I'd written this, one of my colleagues had an insight. This seems to work: Close OutlookUse MFCMAPI to delete the ruleConnect to the mailbox with OWA, which will now see an empty safe sender listAdd a safe sender entry and save the changeExit OWAStart Outlook Now Outlook sees the server-side list as more recent than its cached copy, so the aggregation copies from server->client instead of the other way. I'll do more testing, but it looks like this might be the way out

Hi SpooRancher Thanks for Sharing, If the problem is solved, please Mark As Answer and Finish this thread Cheers Zi FengZi Feng TechNet Community Support

Not quite there yet, I think. There are some issues around whether the Outlook clients use online or cached mode, and I'm seeing some cases where I clean out the rule with MFCMAPI, but an OWA session still sees them. In this case, reconnecting with OWA after a while shows the rule is gone, so I'm suspecting that the rules could be being cached in CAS servers. When I've bottomed this out I'll write up a full procedure to save anyone else having to do all this! Alan

Thanks AlanZi Feng TechNet Community Support