OVH: Bugfix: Native DMARC records rejected for subdomains #3440
Conversation
This file contains 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
Beforehand OVH refused to allow updating native DMARC records that weren't exactly `_dmarc`. This prevents updating `_dmarc` subdomains such as `_dmarc.something`. This change makes that test less strict and allows to now update DMARC records that are subdomains of the zone domain.
tlimoncelli
approved these changes
Feb 17, 2025
|
Looks good! Thanks for the update! |
tlimoncelli
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #3427
Beforehand OVH refused to allow updating native DMARC records that weren't exactly
_dmarc. This prevents updating_dmarcsubdomains such as_dmarc.something. This change makes that test less strict and allows to now update DMARC records that are subdomains of the zone domain.