Seems like a step backwards to me, but at least we know what's happening and have a semi-reasonable workaround. Because using BCC on existing thread breaks rules for some people they've decided to assume that any message you send to a DL using BCC should be moved to the folder you're storing other messages from that thread in, regardless of whether or not you have a rule to move those messages. Please let me know if you have any questions.Īpparently this is "expected behavior". To avoid unintended display of this behavior, please have the senders compose a new message instead of recycling an existing message thread from the Sent Items. The BCC agent detects BCC messages, looks at the In-Reply-To header, searches for the message identified by the In-Reply-To header, and delivers the BCC message to the same folder as the replied-to message. The BCC Transport agent provides this functionality. to discourage members of the DL from sending more replies), that BCC'd reply lands in the recipients' Inboxes, instead of landing in the same folder as the rest of the messages for that DL. The design stems from users who complained that when someone replies to a message on a DL and moves the DL to the BCC line (e.g.
Text Engineering confirmed that the behavior is expected and by design. I've combed through the settings in Outlook (2016/365) and have not found anything that would involve some sort of automatic intelligence to move messages based on how a users has moved them in the past. None of these employees have any inbox or sweep rules. We had a couple other people open tickets saying they never received the message, but in all of those cases we were able to locate the message sitting unread in a different folder. In every case, the message is delivered to the folder in an unread state. In every case, the subfolder the message was delivered to was the folder that the user would likely have moved the message to on their own. We received reports from half a dozen people that the message showed up in a subfolder of their inbox rather than directly in their inbox. In the most recent example, she sent a message to the Everyone dynamic group announcing a new employee. So far it only seems to be happening on messages sent by one of our HR reps. Outlook seems to be gaining consciousness and is automatically organizing messages for people without any inbox rules in place. We've been seeing an odd issue over the past couple weeks.