Skip to content

Commit 6087116

Browse files
authored
Update mta-sts.mdx (cloudflare#21306)
Pulls forward cloudflare#20213
1 parent f138cfd commit 6087116

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

src/content/docs/email-routing/setup/mta-sts.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Next you need an HTTPS endpoint at `mta-sts.example.com` to serve your policy fi
3131

3232
To do this you need to deploy a Worker that allows email clients to pull Cloudflare’s Email Routing policy file using the “well-known” URI convention.
3333

34-
4. Go to your **Account** > **Workers & Pages** and press **Create Application**. Pick the default "Hello World" option button, and replace the sample worker code with the following:
34+
4. Go to your **Account** > **Workers & Pages** and select **Create**. Pick the default "Hello World" option button, and replace the sample worker code with the following:
3535

3636
```js
3737
export default {
@@ -41,7 +41,9 @@ export default {
4141
};
4242
```
4343

44-
5. This Worker proxies `https://mta-sts.mx.cloudflare.net/.well-known/mta-sts.txt` to your own domain. After deploying it, go to the Worker configuration, then **Triggers** > **Custom Domains** and **Add Custom Domain**. Type the subdomain `mta-sts.example.com`.
44+
This Worker proxies `https://mta-sts.mx.cloudflare.net/.well-known/mta-sts.txt` to your own domain.
45+
46+
5. After deploying it, go to the Worker configuration, then **Settings** > **Domains & Routes** > **+Add**. Type the subdomain `mta-sts.example.com`.
4547

4648
![MTA-STS Worker Custom Domain](~/assets/images/email-routing/mta-sts-domain.png)
4749

0 commit comments

Comments
 (0)