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
| Associate an integration with an MX/Inline domain || Required |
112
113
| Add/verify domains | Required | Required |
113
114
|[Update MX records/connector](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/), then allow Cloudflare [egress IPs](/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment-setup/) on downstream mail server || Required |
@@ -117,6 +118,7 @@ Follow the below checklist to ensure your email environment is set up correctly:
117
118
| Configure [text add-ons](/cloudflare-one/email-security/detection-settings/configure-text-add-ons/) and [link actions](/cloudflare-one/email-security/detection-settings/configure-link-actions/)|| Required |
118
119
| Send a test email and verify it appears in **Monitoring** > [**Email activity**](/cloudflare-one/email-security/email-monitoring/#email-activity) with expected disposition | Required | Required |
119
120
120
-
[^1]: Still used for directory/auto‑move insight if desired as well as authorizing free API CASB.
121
+
[^1]: Associating an integration with BCC/Journaling is required for post-delivery but not for pre-delivery.
122
+
[^2]: Still used for directory/auto‑move insight if desired as well as authorizing free API CASB.
121
123
122
124
Now that you know which deployment path to choose, you can begin your onboarding process.
0 commit comments