Skip to content

[Email Security] Update prereq commands #22549

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 21, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ import { Render } from "~/components"

In this tutorial, you will learn how to configure Cisco IronPort with Email Security as MX record.

<Render file="email-security/deployment/mx-deployment-prerequisites"/>
<Render file="email-security/deployment/mx-deployment-prereq"/>

## 1. Add a Sender Group for Email Security Email Protection IPs

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ import { Render } from "~/components"

In this tutorial, you will learn how to configure Google Workspace with Email Security as MX record.

<Render file="email-security/deployment/mx-deployment-prerequisites"/>
<Render file="email-security/deployment/mx-deployment-prereq"/>

## Requirements

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ import { Render, Markdown, GlossaryTooltip } from "~/components"

In this tutorial, you will learn how to configure Microsoft Office 365 with Email Security as its MX record.

<Render file="email-security/deployment/mx-deployment-prerequisites"/>
<Render file="email-security/deployment/mx-deployment-prereq"/>

## 1. Add Email Security IP addresses to Allow List

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,8 +18,7 @@ To check your existing TTL, open a terminal window and run the following command
dig mx <YOUR_DOMAIN>
```

```sh output

```txt output
; <<>> DiG 9.10.6 <<>> mx <YOUR_DOMAIN>
;; global options: +cmd
;; Got answer:
Expand All @@ -29,12 +28,11 @@ dig mx <YOUR_DOMAIN>
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;domain. IN MX
;<YOUR_DOMAIN>. IN MX

;; ANSWER SECTION:
<YOUR_DOMAIN>. 300 IN MX 5 mailstream-central.mxrecord.mx.
<YOUR_DOMAIN>. 300 IN MX 10 mailstream-east.mxrecord.io.
<YOUR_DOMAIN>. 300 IN MX 10 mailstream-west.mxrecord.io.
<YOUR_DOMAIN>. 300 IN MX 10 mxa.global.inbound.cf-emailsecurity.net.
<YOUR_DOMAIN>. 300 IN MX 10 mxb.global.inbound.cf-emailsecurity.net.
```

In the above example, TTL is shown in seconds as `300` (or five minutes).
Expand Down
Loading