Skip to content

[Email Security] Expand MX/Inline configuration deployment page #23121

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
Jun 24, 2025

Conversation

Maddy-Cloudflare
Copy link
Contributor

No description provided.

Copy link
Contributor

hyperlint-ai bot commented Jun 19, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Expanded the MX/Inline configuration deployment page for Email Security with additional details and clarifications.

  • Added a diagram illustrating the inline deployment process.
  • Included instructions for changing MX records to point to Cloudflare.
  • Clarified the importance of setting up Time to Live (TTL) for DNS propagation.
  • Highlighted the benefits of choosing inline deployment for email security.

Modified Files

  • src/content/docs/cloudflare-one/email-security/setup/pre-delivery-deployment/mx-inline-deployment.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

Copy link
Contributor

This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:

Pattern Owners
/src/content/docs/cloudflare-one/ @ranbel, @cloudflare/pcx-technical-writing

@Maddy-Cloudflare Maddy-Cloudflare marked this pull request as draft June 24, 2025 16:21
@Maddy-Cloudflare Maddy-Cloudflare marked this pull request as ready for review June 24, 2025 16:58
Co-authored-by: Patricia Santa Ana <103445940+patriciasantaana@users.noreply.github.com>
@Maddy-Cloudflare Maddy-Cloudflare enabled auto-merge (squash) June 24, 2025 17:38
@Maddy-Cloudflare Maddy-Cloudflare merged commit ca835f7 into production Jun 24, 2025
11 checks passed
@Maddy-Cloudflare Maddy-Cloudflare deleted the maddy/email-security-pcx-17697 branch June 24, 2025 17:50
sdnts pushed a commit to sdnts/cloudflare-docs that referenced this pull request Jul 24, 2025
…dflare#23121)

* [Email Security] Expand MX/Inline configuration deployment page

* sentence clarifications

* Change order (TTL comes before MX changes)

* Correct content

* Minor update

* Apply suggestions from code review

Co-authored-by: Patricia Santa Ana <103445940+patriciasantaana@users.noreply.github.com>

---------

Co-authored-by: Patricia Santa Ana <103445940+patriciasantaana@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants