Michael: I ran the "Get-MailboxJunkEmailConfiguration" to show which users still had it enabled and most of the ones that still show as "True" have possibly never logged into the mailbox-though it does exist in EMC. There was one user erroring out, but turned out she had addresses listed in her Junk mail settings. Once cleared, we were able to complete the Set-MailboxJunkEmailConfiguration on her mailbox successfully. I was asked to turn it off across the board, which has failed, but I think I've successfully disabled it against all users that have ever logged into their mailboxes. Some of the failures are generic accounts (which have mailboxes in EMC), but likely users are not actively logging into them (inherited AD/server config that we're sorting through).
Thanks. From: [email protected] [mailto:[email protected]] On Behalf Of Michael B. Smith Sent: Thursday, February 20, 2014 3:15 PM To: [email protected] Subject: [Exchange] RE: Disabling Email Going to Junk Folder Generally speaking, when I've seen that error before, it means that the mailbox has not actually been created. If that isn't the case for you, I'd like to see results from Get-Mailbox, Get-MailboxStatistics, and a Set-MailboxJunkEmailConfiguration -Verbose. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Geoff Orlebeck Sent: Wednesday, February 19, 2014 5:39 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] Disabling Email Going to Junk Folder We have a single Exchange 2010 SP3 UR4 (clients running Outlook 2010) protected by third party spam filter. Trying to disable the Junk email via "Set-MailboxJunkEmailConfiguration -Enabled $false" and I get a couple errors about "The user needs to sign in to OWA before they can modify their Safe Senders and Recipients or Blocked Senders List". I just want to make sure if the user sets this via OWA, it's a universal setting that doesn't also have to be tweaked within their Outlook profile as well. Can anyone confirm that is the case? Thank you. -Geoff This message and any attached documents may be privileged or confidential and contain information protected by state and federal privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. This message and any attached documents may be privileged or confidential and contain information protected by state and federal privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender.
