[FIX] mail: move subdomain DNS setup from website to inbound mail doc#18187
Open
jupe-odoo wants to merge 1 commit into
Open
[FIX] mail: move subdomain DNS setup from website to inbound mail doc#18187jupe-odoo wants to merge 1 commit into
jupe-odoo wants to merge 1 commit into
Conversation
Collaborator
|
|
jqu-odoo
reviewed
Jun 1, 2026
jqu-odoo
reviewed
Jun 1, 2026
jupe-odoo
force-pushed
the
17.0-update-subdomain-mailing-jupe
branch
from
0c43237 to
9ab9035
Compare
jupe-odoo
force-pushed
the
17.0-update-subdomain-mailing-jupe
branch
from
9ab9035 to
15a9812
Compare
jupe-odoo
force-pushed
the
17.0-update-subdomain-mailing-jupe
branch
2 times, most recently
from
9b56210 to
0df49ef
Compare
jupe-odoo
commented
Jun 5, 2026
Abridbus
reviewed
Jun 8, 2026
jupe-odoo
force-pushed
the
17.0-update-subdomain-mailing-jupe
branch
from
0df49ef to
aea6877
Compare
jupe-odoo
changed the title
jupe-odoo
force-pushed
the
17.0-update-subdomain-mailing-jupe
branch
from
aea6877 to
56de68b
Compare
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
jupe-odoo
force-pushed
the
17.0-update-subdomain-mailing-jupe
branch
from
56de68b to
f0dd2e5
Compare
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
4 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