Mail Flow - External Message Warning HELP

Anonymous
2019-02-11T17:13:35+00:00

Hello!

I'm trying to setup a mail flow rule for external email messages from non-organization addresses. I have it setup great, however I have it coded so that it displays the yellow background, red boarder etc and it displays perfect in a sample code viewer. However, when I add it to my rule and then send a test message to my email from outside the org, it doesn't display any of these colors. HELP?? I have included my code below. I'm using 0365

<div style="background-color:#FFEB9C; width:100%; border-style: solid; border-color:#9C6500; border-width:1pt; padding:2pt; font-size:10pt; line-height:12pt; font-family:'Calibri'; color:Black; text-align: left;"><span style="color:#9C6500"; font-weight:bold;>CAUTION:</span> This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.</div><br>

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2019-02-11T19:26:52+00:00

Hi BH33,

Thanks for provide the details in your post. About your question, please kindly check following steps to see if it can help you fix this issue:

  1. In Exchange Admin Center, go to mail flow > rules and then click "+" to create a new rule.
  2. Then set the new rule like below picture:

Note: in step 4, please enter following code: 

<p><div style="background-color:#FFEB9C; width:100%; border-style: solid; border-color:#9C6500; border-width:1pt; padding:2pt; font-size:10pt; line-height:12pt; font-family:'Calibri'; color:Black; text-align: left;"><span style="color:#9C6500"; font-weight:bold;>CAUTION:</span> This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.</div><br></p>

I have tested above rule on my side and I can successfully show the warning message(see below picture), if you have any problems when doing so, please feel free to post back and provide us a screenshoot of the detailed information about the rule you created for analysis.

Regards,

Jennifer

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments

93 additional answers

Sort by: Newest
  1. Anonymous
    2020-07-10T17:17:12+00:00

    We are 100% cloud based for Outlook/Exchange.

    Can you send me the rule offline @ jkuterba@microsoft.com

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2020-07-10T16:33:22+00:00

    We are 100% cloud based for Outlook/Exchange.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-07-08T17:04:22+00:00

    Sounds like you may not have your apply rules quite right.

    Apply this rule if.... - The sender is located... "Outside the organization"

    and

    Apply this rule if... - The recipient is located... "Inside the organization"

    Hi Neal,

    Thanks for your reply. I have this rule set as per the instruction. External email are getting the warning message. But when an internal user send an email to internal dl, the emails are marked as external. 

    Where are your DLs.  are they On-prem or in the cloud.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-07-08T16:17:58+00:00

    Sounds like you may not have your apply rules quite right.

    Apply this rule if.... - The sender is located... "Outside the organization"

    and

    Apply this rule if... - The recipient is located... "Inside the organization"

    Hi Neal,

    Thanks for your reply. I have this rule set as per the instruction. External email are getting the warning message. But when an internal user send an email to internal dl, the emails are marked as external.

    Was this answer helpful?

    0 comments No comments