Forum Discussion
Stephanie_Grammar
Feb 10, 2022Copper Contributor
Messages from internal user going to Junk for only one other internal user
Hi all, I am just about out of ideas of what could be causing this problem and have tried everything I could think of and find when researching similar issues, so I'm turning to the Microsoft com...
- Feb 15, 2022
Stephanie_GrammarHad a similiar problem a few years back at a customer.
Turned out to be a separate junk-rule in the CEO smartphone Samsung mail app. The rule was only visible and active in this app and showed neither in Outlook nor Exchange.
At one time before he clicked his assistences mail in his Samsung Mail App as "mark as spam". Everytime his smartphone did an ActiveSync-run he moved her mails in junk.
Greetings
ExMSW4319
Feb 15, 2022Iron Contributor
Problem only happens for mail from COO to CMO, and for no other combination of sender and recipient in your org? The problem is at the CMO end, acting on some property of the COO mail.
The remedial Inbox rule saves the message, which then gets put back in Junk? Something else is acting on the CMO mailbox. Does the CMO have any delegates? Is there a second device involved?
The remedial Inbox rule saves the message, which then gets put back in Junk? Something else is acting on the CMO mailbox. Does the CMO have any delegates? Is there a second device involved?
Stephanie_Grammar
Feb 15, 2022Copper Contributor
There did end up being a second device that was causing the problem - CMO had a Samsung mobile device that he'd accidentally marked the COO as spam on, which added him to the Spam Sender list. Seems like because of the way the mailbox sync operates, the reason why it would look like it would stick and then disappear was anytime we moved it from Junk to the inbox, it would sync that update across devices and the mailbox rule from the mobile device apparently takes precedence over all others (doesn't make much sense to me as to *why* that is the case, but I'm still a newb).
Once we got that removed, everything worked as it should again.
Once we got that removed, everything worked as it should again.