[FIX] mail: move subdomain DNS setup from website to inbound mail doc - #19220
Open
fw-bot wants to merge 1 commit into
Open
[FIX] mail: move subdomain DNS setup from website to inbound mail doc#19220fw-bot wants to merge 1 commit into
fw-bot wants to merge 1 commit into
Conversation
Collaborator
|
|
Collaborator
Author
|
@jupe-odoo cherrypicking of pull request #18187 failed. stdout: Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).
More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port |
you can use 
The inbound mail documentation referred to the subdomain-based method as "MX record", which was too narrow and confusing. Both CNAME and MX records are valid options, but CNAME is simpler to set up as it inherits SPF and other DNS records from the target domain, avoiding extra configuration for outbound mail authentication. The setup instructions were also scattered across the website/domain_names documentation, which is not where users configuring inbound mail would naturally look. In email_servers_inbound.rst, the section is renamed to "DNS records" and consolidated with step-by-step instructions for both Odoo Online and Odoo.sh, recommending CNAME while keeping MX as a noted alternative. All cross-references in email_communication.rst, email_servers_outbound.rst, and domain_names.rst are updated accordingly. task-6191004 X-original-commit: 0ae232b
jupe-odoo
force-pushed
the
19.0-17.0-update-subdomain-mailing-jupe-552278-fw
branch
from
August 3, 2026 07:11
5d3aee3 to
1fb2c91
Compare
Contributor
|
Hello @mcsi-odoo, there was a minor conflict between two sentences, which I’ve corrected. I’ll need your R+ to proceed with the port forwarding. Thanks! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The inbound mail documentation referred to the subdomain-based method
as "MX record", which was too narrow and confusing. Both CNAME and MX
records are valid options, but CNAME is simpler to set up as it inherits
SPF and other DNS records from the target domain, avoiding extra
configuration for outbound mail authentication.
The setup instructions were also scattered across the website/domain_names
documentation, which is not where users configuring inbound mail would
naturally look.
In email_servers_inbound.rst, the section is renamed to "DNS records"
and consolidated with step-by-step instructions for both Odoo Online
and Odoo.sh, recommending CNAME while keeping MX as a noted alternative.
All cross-references in email_communication.rst, email_servers_outbound.rst,
and domain_names.rst are updated accordingly.
task-6191004
Forward-Port-Of: #18187