Forum Discussion
BCC Foldering Agent
Not well documented, but this looks like expected behavior:
"Engineering confirmed that the behavior is expected and by design. 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. 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 BCC Transport agent provides this functionality. 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." (source)Were not able to repro the folder movement; messages did have an extra header, X-MS-Exchange-Processed-By-BccFoldering
Not well documented, but this looks like expected behavior:
"Engineering confirmed that the behavior is expected and by design. 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. 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 BCC Transport agent provides this functionality. 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." (source)
Were not able to repro the folder movement; messages did have an extra header, X-MS-Exchange-Processed-By-BccFoldering
Thanks Michel, this indeed is the same what we have experienced and it seems to be the root cause. What I'd add to the obeservations from the forum thread you cited: it doesn't have to be a DL in the BCC field, it occurs even when simply a couple of user mailboxes are BC-ed.
We had this same issue with our systems. Our scenario might not match yours exactly, but we have an email account that is used to process important emails. It was a lights out system and our employees would include this email account on the BCC line if we needed to track it. The trouble is BCC Foldering was moving it on us before we got a chance to have it processed by some automated tools.
Our work around was we setup a new 0365 Group email (think DL) that our Employees started using instead on the BCC line. Then we setup an mail flow Rule on Exchange to take all emails sent to this email do a Redirect to the custom email account that our tools are running against. The result is the BCC header is stripped from the email, and no BCC Foldering kicks in.
Hope this helps.
