diff --git a/src/assets/images/email-security/deployment/inline-setup/CF_A1S_Deployment_Inline_Diagrams.png b/src/assets/images/email-security/deployment/inline-setup/CF_A1S_Deployment_Inline_Diagrams.png new file mode 100644 index 000000000000000..7cd838c8b3eb964 Binary files /dev/null and b/src/assets/images/email-security/deployment/inline-setup/CF_A1S_Deployment_Inline_Diagrams.png differ diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx new file mode 100644 index 000000000000000..d659ffda51d84f1 --- /dev/null +++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/index.mdx @@ -0,0 +1,14 @@ +--- +title: Pre-delivery deployment +pcx_content_type: navigation +sidebar: + order: 1 + group: + hideIndex: true +--- + +import { DirectoryListing } from "~/components" + + + + \ No newline at end of file diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/inline-deployment-setup.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/inline-deployment-setup.mdx new file mode 100644 index 000000000000000..8a5b6aec0cbcc87 --- /dev/null +++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/inline-deployment-setup.mdx @@ -0,0 +1,57 @@ +--- +title: Set up inline deployment +pcx_content_type: concept +sidebar: + order: 2 +--- + +To set up MX Inline: + +1. Log in to [Zero Trust](https://one.dash.cloudflare.com/). +2. Select **Email Security**. +3. Select **Monitoring**. If you are a first time user, select **Contact sales**. Otherwise, select **Set up**. +4. Select **MX/Inline**. +5. To start the MX/Inline configuration, you will have to completed the prerequisite setup on your email provider's platform. Once you have completed this step, select **I confirm that I have completed all the necessary requirements**. Then, select **Start configuration**. + +If you have verified zones on Cloudflare, continue with the following steps: + +1. **Connect a domain**: Select your domain. Then, select **Continue**. +2. **Select position**: This step allows you to choose where Email Security fits into your mail flow and configure position settings: + - **Select position**: Choose between: + - **Sit first (hop count = 1)**: Email Security sits at the first hop. There are no other email scanners or services between the Internet and Cloudflare. + - **Sit in the middle (hop count > 1)**: Email Security sits in the middle of your email processing. There are other email scanners or email services in between. + - **Position settings**: Refine how Email Security receives and forwards emails: + - **Forwarding address**: This is your mail flow next hope after Email Security. This value is auto-filled, but you can still change it. + - **Outbound TLS**: Choose between: + 1. **Forward all messages over TLS** (recommended). + 2. **Forward all messages using opportunistic TLS**. + - Select **Continue**. +3. (Optional) **Configure quarantine policy**: Select dispositions to automatically prevent certain types incoming messages from reaching a recipient's inbox. +4. (Optional ) **Update MX records**: + - Email Security can automatically update MX records for domains that proxy traffic through Cloudflare. Under your mail processing location, select one of the following: + - Global (Recommended) + - US + - EU +5. **Review details**: Review your domain, then select **Go to domains**. + +## Users who do not have domains with Cloudflare + +If you do not have domains with Cloudflare, the dashboard will display two options: + +- Add a domain to Cloudflare. +- Enter domain manually. + +### Add a domain to Cloudflare + +Selecting **Add a domain to Cloudflare** will redirect you to a new page where you will connect your domain to Cloudflare. Once you have entered an existing domain, select **Continue**. + +Then, follow the steps to [Set up MX/Inline](/cloudflare-one/email-security/setup/pre-delivery-deployment/inline-deployment-setup/). + +### Enter domain manually + +1. **Add domains**: Manually enter domain names. +2. **Review all domains**: Review all your domains, then select **Continue**. +3. **Verify your domains**: It may take up to 24 hours for your domains to be verified. Select **Done**. +4. Once your domains have been verified, the dashboard will display a message like this: **You have verified domains ready to connect to Email Security**. This means that you can now set up Email Security via MX/Inline. +5. Select **Set up**, then select **MX/Inline**. +6. Follow the steps to [Set up MX/Inline](/cloudflare-one/email-security/setup/pre-delivery-deployment/inline-deployment-setup/). \ No newline at end of file diff --git a/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/inline-deployment.mdx b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/inline-deployment.mdx new file mode 100644 index 000000000000000..b36374a53910b4e --- /dev/null +++ b/src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/inline-deployment.mdx @@ -0,0 +1,20 @@ +--- +title: Inline deployment +pcx_content_type: concept +sidebar: + order: 1 +--- + +With pre-delivery deployment, also known as Inline deployment, Email Security evaluates email messages before they reach a user's inbox. + +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. + +When you choose an inline deployment, you get the following benefits: + +- Messages are processed and physically blocked before delivery to a user's mailbox. +- Your deployment is simpler, because any complex processing can happen downstream and without modification. +- Email Security can modify delivered messages, adding subject or body mark-ups. +- Email Security can offer high availability and adaptive message pooling. +- You can set up advanced handling downstream for non-quarantined messages with added X-headers. + +![Inline deployment diagram](~/assets/images/email-security/deployment/inline-setup/CF_A1S_Deployment_Inline_Diagrams.png) \ No newline at end of file