Repository navigation
docs: add note regarding email security and DNS policies for subdomains - #12727
Closed
MatrixNeoKozak wants to merge 1 commit into
Conversation
|
❌ PR description validation failed due to being incorrectly formatted.
|
MattIPv4
requested changes
Oct 12, 2026
Member
There was a problem hiding this comment.
This makes no sense, subdomain owners do not have DNS control to set SPF/DMARC records.
Activity of this account looks to be automated AI PRs: https://github.com/MatrixNeoKozak
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
2 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.
What
Clarify email security policies and DMARC/SPF recommendations for subdomains as per issue #10151.
Why
This change resolves the target issue or improvement.
How to test
Verify that the project builds/runs correctly and the specific bug/improvement is addressed.
Fixes #10151