What is the meaning of jmr:0 or jmr:1 in the X-Microsoft-Antispam-Mailbox-Delivery (i.e ucf:0;jmr:1;auth:0;dest:J;ENG:(910001)(944506458)(944626604)(750132)(520011016)?

Question

Hello,
We have a few MSFT accounts. One of them is landing into spam when delivering emails to another Exchange, Outlook, or live account.
Looking at the headers, the only difference that I can see is the jmr:0 or jmr:1 .

What is the meaning of these letters and numbers?

Pierre

Answer 1

Hi @Pierre Pignault ,

Welcome to post in Microsoft Q&A!

We have a few MSFT accounts.

Could you clarify it a bit more about what you mean by "MSFT accounts"? Are you using Microsoft personal accounts like outlook.com or you are referring to Microsoft 365 account which connecting to the Exchange online service?

Regarding your concern about the "jmr:0 or jmr:1 in the X-Microsoft-Antispam-Mailbox-Delivery" header, I've tried searching a lot but so far cannot find any documentation explictly stating this. Then I tested in my lab tenant, trying to make mails from an external sender arrive in Junk Email folder using different methods, and based on my test results, the following two scenarios can lead to "jmr:1":

• The SCL of the messages is equal or higher than 5, which by default will make the mails end up in Junk Email folder.
  During my tests, I tried setting the SCL of messages from a paricular sender to 6 using mail flow rule, and noticed that jmr:1 is included in the X-Microsoft-Antispam-Mailbox-Delivery header:
  
  

For more information about SCL, hopefully you can find the articles below useful:
Spam confidence level (SCL) in EOP
Use mail flow rules to set the spam confidence level (SCL) in messages in Exchange Online

• The message sender is set as a blocked sender in the Junk Email options:
  
  Other scenarios I tried including creating Inbox rules to move messages to Junk Email folder, but it shows jmr:0:
  

Noticed you've mentioned issue occurs when dilivering to different accounts, so personally I don't think the block sender added in the Junk Email options on the recipients could be the cause. So given this, I'd recommend comparing the SCL score of messages from this problematic account with the mails from the other accounts, if the mails went to spam all have a higher SCL, you may need to investigate further into this point. To see the SCL value, we can copy the entire message header into this website, then click "Analyze headers", search for "SCL" or check the header mentioned in my screenshots earlier.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Further to above testing below is my findings on a similar issue where the email is delivered to Junk folder.

If you see below in the email header with SCL 1 and SFV: NSPM then please do check the following attribute 'TrustedListsOnly' in 'Get-MailboxJunkEmailConfiguration'.

X-Microsoft-Antispam-Mailbox-Delivery:
ucf:0;jmr:0;ex:1;auth:0;dest:J;OFR:SpamFilterAuthJ;ENG:(910001)(944506478)(944626604)(920097)(890001)(250001)(435001)(930097)(3100021);RF:JunkEmail;

If this is set to True then "Only messages from email address or domain entries in the Safe Senders list and the Safe Recipients list are delivered to the Inbox. All other messages are automatically delivered to the Junk Email folder".

Default value should be 'False'. You can use 'Set-MailboxJunkEmailConfiguration -TrustedListsOnly $false'.

Reference document:
https://learn.microsoft.com/en-us/powershell/module/exchange/set-mailboxjunkemailconfiguration?view=exchange-ps