Forum Discussion
Transport rule for authenticated sender
- Jul 09, 2020
VasilMichevThanks for the input. I might just have found the answer..
Ran Extended message trace and found this "DefaultFolderType:JunkEmail-Mailbox Rules Agent" in the column "recipient_status".
Checked recipient mailbox and found inbox rules that check for some random words in message body and move the message to Junk Mail folder. This was probably in place as a form for protection against spam in pre-EOP times.
Removed the inbox rule, hoping the problem is solved.
And i now notice the difference in headers between messages that were affected by this rule.
Message in inbox: X-Microsoft-Antispam-Mailbox-Delivery: ucf:0;jmr:0;auth:0;dest:I
Message in junk: X-Microsoft-Antispam-Mailbox-Delivery: ucf:1;jmr:0;auth:0;dest:J;OFR:CustomRules
Would be nice to see X-Microsoft-Antispam-Mailbox-Delivery documented, but this is probably not happening soon. 🙂 BR, Ruslan
Since you've already checked both message trace and the relevant headers, I'd suggest opening a support case.
VasilMichevThanks for the input. I might just have found the answer..
Ran Extended message trace and found this "DefaultFolderType:JunkEmail-Mailbox Rules Agent" in the column "recipient_status".
Checked recipient mailbox and found inbox rules that check for some random words in message body and move the message to Junk Mail folder. This was probably in place as a form for protection against spam in pre-EOP times.
Removed the inbox rule, hoping the problem is solved.
And i now notice the difference in headers between messages that were affected by this rule.
Message in inbox: X-Microsoft-Antispam-Mailbox-Delivery: ucf:0;jmr:0;auth:0;dest:I
Message in junk: X-Microsoft-Antispam-Mailbox-Delivery: ucf:1;jmr:0;auth:0;dest:J;OFR:CustomRules
Would be nice to see X-Microsoft-Antispam-Mailbox-Delivery documented, but this is probably not happening soon. 🙂 BR, Ruslan