This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 72%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
Hello all,
with the recent November patch for Exchange (Exchange 2016, CU23), our autoreplies generated by our exchange server get flagged as suspicious (https://learn.microsoft.com/en-us/exchange/plan-and-deploy/post-installation-tasks/security-best-practices/exchange-non-compliant-p2from-detection?view=exchserver-2019 ). autoreplies are generated by rule "Apply this rule after message arrives where sent to ******@address.com have server reply using <email template>". I don't see any options in the email template to modify header options.
Has anyone else seen this?
Florian
This is an Outlook rule, yes? Not an Exchange rule.
it's a serverside rule attached to the mailbox (Get-InboxRule -Mailbox ******@address.com does list it)
yea thats an Outlook rule. :)
you could always override the new behavior. Not recommended but possible:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 90%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAZ%3C/text%3E%3C/svg%3E)
Hello, @fzb,
Welcome to the Microsoft Q&A platform!
Andy David - MVP is right. According to Microsoft's latest documentation, this detection behavior is recommended to be turned on because it can help you with phishing attacks. However, if you want to disable it, you can use the New-SettingOverride command from an elevated Exchange Management Shell (EMS) to override the new behavior.
The command template is as follows：
New-SettingOverride -Name "DisableNonCompliantP2FromProtection" -Component "Transport" -Section "NonCompliantSenderSettings" -Parameters @("AddDisclaimerforRegexMatch=false") -Reason "Disabled For Troubleshooting"
Get-ExchangeDiagnosticInfo -Process Microsoft.Exchange.Directory.TopologyService -Component VariantConfiguration -Argument Refresh
Restart-Service -Name MSExchangeTransport
If the answer is helpful please click on ACCEPT ANSWER as it could help other members of the Microsoft Q&A community who have similar questions and are looking for solutions.
Thank you for your support and understanding.
Best Wishes,
Alex Zhang