Document SES MAIL FROM domain records#18
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8d21865982
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| | Email signing | CNAME | Both modes | Enables DKIM signing through Amazon SES. | | ||
| | Sending policy | TXT | Both modes | Authorises Sendmux to send for the domain. | | ||
| | Message policy | TXT | Both modes | Defines DMARC handling for suspicious mail. | | ||
| | Bounce handling | MX and TXT | Both modes | Routes bounce handling through a subdomain. | |
There was a problem hiding this comment.
With this new row, sending-only domains now require an MX record on bounce.{domain}, but the earlier copy-DNS step still says sending-only domains “do not show or check an MX record.” That contradiction can lead sending-only users to skip the required bounce MX or think the table is wrong; please qualify the earlier sentence as the inbound/domain MX, or call out that the bounce subdomain MX is still required.
Useful? React with 👍 / 👎.
1 participant
Summary
Verification