You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you deploy Email Security via MX/Inline, you will have to change your MX records to point to Cloudflare. An MX record is a [DNS record](/dns/manage-dns-records/). If your DNS records are hosted by Cloudflare (or any other provider, except for Google), you can [edit your DNS records](/dns/manage-dns-records/how-to/create-dns-records/#edit-dns-records) via the dashboard or the API to point your MX records to Cloudflare.
13
+
14
+
By changing your MX records, Email Security will be positioned between your incoming emails and Microsoft 0365 or Gmail.
15
+
16
+
When you change your MX records, you will also have to set up the [Time to Live (TTL)](/dns/manage-dns-records/reference/ttl/). If you do not set up the TTL, the DNS propagation will take longer to happen. By reducing the TTL, you are decreasing the time it takes for DNS records to propagate.
17
+
10
18
Email Security becomes a hop in the SMTP processing chain and physically interacts with incoming email messages. Based on your policies, various messages are blocked before reaching the inbox.
11
19
12
20
When you choose an inline deployment, you get the following benefits:
@@ -15,6 +23,4 @@ When you choose an inline deployment, you get the following benefits:
15
23
- Your deployment is simpler, because any complex processing can happen downstream and without modification.
16
24
- Email Security can modify delivered messages, adding subject or body mark-ups.
17
25
- Email Security can offer high availability and adaptive message pooling.
18
-
- You can set up advanced handling downstream for non-quarantined messages with added X-headers.
0 commit comments