{"id":5262,"date":"2022-01-21T11:59:49","date_gmt":"2022-01-21T16:59:49","guid":{"rendered":"https:\/\/www.exchangedefender.com\/blog\/?p=5262"},"modified":"2022-01-21T11:59:50","modified_gmt":"2022-01-21T16:59:50","slug":"flexible-allow-policy-whitelisting-for-mass-mailers-bats","status":"publish","type":"post","link":"https:\/\/www.exchangedefender.com\/blog\/2022\/01\/flexible-allow-policy-whitelisting-for-mass-mailers-bats\/","title":{"rendered":"Flexible Allow Policy (Whitelisting) For Mass Mailers \/ BATS"},"content":{"rendered":"\n
<\/div>\n\n\n\n

Caveat: This feature is not recommended by ExchangeDefender, we actively discourage you from using it, and it is disabled by default. At the same time, we understand that sometimes the risk of getting hacked is less painful than arguing with non-technical users… In other words, we got you.<\/em><\/p>\n\n\n\n

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

ExchangeDefender is an SMTP proxy security service, we scrub your email and only pass on stuff that doesn’t look like SPAM. In order to make that happen, we use industry standards such as SPF, DKIM and DMARC to make sure the senders are legitimate. (envelope-sender<\/em> aka “envelope from:”<\/em>)<\/p>\n\n\n\n

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

The challenge these days is that nearly all the automated email messages (password reminders, marketing messages, newsletters, order confirmations, 2FA\/OTP, etc) are sent from a unique disposable email address. Instead of coming from\u00a0orders@amazon.com<\/a>\u00a0(the email you see in Outlook\/Gmail) they actually come from something like vlad=exchangedefender-com.23581.i32.1941kab@east-1.aws.amazon.com<\/em>. These email addresses are automatically generated and only live for a short period of time (less than 24 hours) and are used to track bounces and failed deliveries. However, once you open the email your mail client looks at the “display from”<\/em> address such as\u00a0orders@amazon.com<\/a>. This address can be forged easily by anyone and that is how hackers end up compromising end users easily (cyberattack process better known as “spear phishing<\/em>“).<\/p>\n\n\n\n

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

ExchangeDefender has a secure facility to manage legitimate newsletter senders and automated email platforms (Domain Admin > Advanced Settings > Bulk Mailer Policy) and we train our partners how to properly create allow policies for<a href=”https:\/\/www.exchangedefender.com\/docs\/whitelist<\/a>“>Disposable Email Addressing<\/a>\/BATS. If you’re not a fan of using that process, you’re going to love the new From: Policy <\/strong>feature.<\/p>\n\n\n\n

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

ExchangeDefender From: Policy<\/strong><\/p>\n\n\n\n

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

ExchangeDefender Advanced Features has a new section called “From: Policy”<\/strong> which enables you to create an Allow Policy based on the Display From address (display-from<\/em>\/fake-from<\/em>). You can find this new setting at\u00a0admin.exchangedefender.com<\/a>\u00a0under Domain Admin > Advanced Features > From: Policy.<\/p>\n\n\n\n

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

The policy is disabled by default, but if you enable it ExchangeDefender will search the email headers for the From: address and apply your Allow Policy (whitelist) using that address. Allow Policy forces ExchangeDefender to bypass all SPAM checks and will deliver the message to the users Inbox regardless of SPAM content (malware protection, virus protection, file attachment policies will still be enforced).<\/p>\n\n\n\n

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

This feature will make delivery of automated messages (newsletters, password reminders, etc) much smoother with the side effect of making it easier for your users to get spear phished. However, this level of security exactly the same as whitelist\/allow policy\/trusted senders evaluations consumer email solutions such as Microsoft365\/Outlook\/Google Apps have, so if you trust their email security you can trust this as well.<\/p>\n\n\n\n

-Vlad<\/p>\n\n\n\n

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

tl;dr;<\/strong> You can now whitelist by the fake email address you see in Outlook\/Gmail.<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"

[…]<\/p>\n","protected":false},"author":50,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5262","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5262","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\/50"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/comments?post=5262"}],"version-history":[{"count":6,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5262\/revisions"}],"predecessor-version":[{"id":5269,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/posts\/5262\/revisions\/5269"}],"wp:attachment":[{"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/media?parent=5262"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/categories?post=5262"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exchangedefender.com\/blog\/wp-json\/wp\/v2\/tags?post=5262"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}