{"id":5951,"date":"2023-07-05T20:51:59","date_gmt":"2023-07-06T00:51:59","guid":{"rendered":"https:\/\/www.exchangedefender.com\/blog\/?p=5951"},"modified":"2023-07-06T11:58:39","modified_gmt":"2023-07-06T15:58:39","slug":"trusted-sender-keeps-on-ending-up-in-spam","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2023\/07\/trusted-sender-keeps-on-ending-up-in-spam\/","title":{"rendered":"Trusted sender keeps on ending up in SPAM<\/strong>"},"content":{"rendered":"\n
<\/div>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

One of the most common complaints we get from our clients has to do with allow\/whitelist policies and to make the long story short this happens because of the way your service provider configured ExchangeDefender. The long story, technical background, and best practices are outlined at https:\/\/www.exchangedefender.com\/docs\/whitelist<\/a>. It usually sounds like this:<\/p>\n\n\n\n

<\/div>\n\n\n\n

\u201cI keep whitelisting this email address that sends me my OTP password \/ password reminder \/ login code \/ transaction confirmation \/ newsletter and they keep on ending up in SPAM!\u201d<\/em><\/h4>\n\n\n\n
<\/div>\n\n\n\n

This happens for clients that configure ExchangeDefender to block email forgeries and spoofing.<\/em><\/p>\n\n\n\n

<\/div>\n\n\n\n

You see, the email address that is showing up in ExchangeDefender and your Outlook\/Gmail is not the actual email address that the message was sent from. Large volume emails (OTP, password reminders, notifications) are not sent by humans, they are computer generated and there is a random email address for every notification they sent out (so when\/if it bounces they can track it).<\/p>\n\n\n\n

<\/div>\n\n\n\n

These automated email addresses tend to have a long randomly generated identifier in them and generally look like this:<\/p>\n\n\n\n

<\/div>\n\n\n\n

010001890676a389-ee862f60-d7ea-4ba1-a113-f16935e2afeb-000000@amazonses.com<\/strong><\/p>\n\n\n\n

<\/div>\n\n\n\n

But in your Outlook\/Gmail the spoofed\/faked email appears to have come from DoNotReply@someotpsite.cz<\/a> which has the domain you trust and attempt to allow\/whitelist. If you pull up the SMTP headers from the quarantined email you can see this email address in the envelope-from<\/strong> field:<\/p>\n\n\n\n

<\/div>\n\n\n\n

Received: from inbound10.exchangedefender.com (65.99.255.114) by
\u00a0owa.exchangedefenderdemo.com (10.10.10.5) with Microsoft SMTP Server (TLS) id 14.3.498.0;
\u00a0Thu, 29 Jun 2023 05:23:03 -0400
Received-SPF: pass (inbound10.exchangedefender.com: domain of 010001890675c389-ee862f60-d7ea-4ba1-a113-f16935e2afeb-000000@amazonses.com designates 54.240.77.69 as permitted sender) receiver=inbound10.exchangedefender.com; client-ip=54.240.77.69; helo=a77-69.smtp-out.amazonses.com; envelope-from=010001890676a389-ee862f60-d7ea-4ba1-a113-f16935e2afeb-000000@amazonses.com<\/mark>; x-software=ExchangeDefender SPF;
Authentication-Results: inbound10.exchangedefender.com; dmarc=pass (p=quarantine dis=none) header.from=someotpsite.cz
Authentication-Results: inbound10.exchangedefender.com;
\u00a0dkim=pass (1024-bit key) header.d=someotpsite.cz header.i=@someotpsite.cz header.b=”QPv3HP79″;
\u00a0dkim=pass (1024-bit key) header.d=amazonses.com header.i=@amazonses.com header.b=”MsX8RGl7″
Received: from a77-69.smtp-out.amazonses.com (a77-69.smtp-out.amazonses.com
\u00a0[54.240.77.69]) by inbound10.exchangedefender.com (8.14.7\/8.14.7) with ESMTP
\u00a0id 35T9M86a030204
<demo@exchangedefenderdemo.com>; Thu, 29 Jun 2023 05:22:09 -0400
From: <DoNotReply@someotpsite.cz><\/mark>
To: <demo@exchangedefenderdemo.com>
Subject: ConnectWise Manage Security Code
…<\/p><\/blockquote><\/figure>\n\n\n\n

<\/div>\n\n\n\n

Solving this issue requires your ExchangeDefender admin to decide how permissive they want to be of email forgeries and fakes. ExchangeDefender provides two ways to manage this in the ExchangeDefender Domain Admin app at https:\/\/admin.exchangedefender.com<\/a> (see documentation<\/a>)<\/p>\n\n\n\n

<\/div>\n\n\n\n

Option 1: Allow email from the bulk email network<\/h2>\n\n\n\n
<\/div>\n\n\n\n

ExchangeDefender enables you to automatically pass through messages coming from specific bulk\/spam mail providers. It\u2019s located at https:\/\/admin.exchangedefender.com<\/a> under Advanced Features > Bulk Mailer Policy<\/strong>:<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

In our example SMTP header the message came from AmazonSES so if you change the policy from Scan to Allow, ExchangeDefender will simply deliver these messages to your mailbox without quarantining it as a forgery\/spoof (which it is).<\/p>\n\n\n\n

<\/div>\n\n\n\n

Option 2: Choose a relaxed From: policy<\/h2>\n\n\n\n
<\/div>\n\n\n\n

This is a less secure option that will allow forgeries and effectively lowers your security level to that of M365\/Office365 \u2013 and we strongly discourage you from doing that. However, if the client requires it you can get it done under Advanced Features > From: Policy<\/strong>:<\/p>\n\n\n\n

<\/div>\n\n\n\n
\"\"<\/a><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Summary<\/strong><\/h4>\n\n\n\n

If you\u2019re seeing notification emails in your SPAM quarantine even though you\u2019ve trusted the sender repeatedly, it\u2019s doing so because the message is being spoofed and your admin has configured ExchangeDefender to block that activity. You can relax the security restrictions by choosing to either allow the bulk mail network or you can build your trust rules on the less-secure From: address.<\/p>\n\n\n\n

<\/div>\n\n\n\n

Our team is always here to help but they aren\u2019t allowed to guess without seeing the SMTP headers first \u2013 so if you ever run into an issue that you\u2019d like us to take a look at grab the headers and provide them at https:\/\/support.exchangedefender.com<\/a> and we\u2019ll advise from there.<\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,1],"tags":[51,32,40,101],"class_list":["post-5951","post","type-post","status-publish","format-standard","hentry","category-exchangedefender","category-uncategorized","tag-email","tag-exchangedefender","tag-security","tag-spam-filtering"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5951","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=5951"}],"version-history":[{"count":20,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5951\/revisions"}],"predecessor-version":[{"id":5977,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5951\/revisions\/5977"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=5951"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=5951"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=5951"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}