Fix missing SPFSyntaxError when ip address and version are not matching #87
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
seanthegeek
added a commit
that referenced
this pull request
Dec 20, 2022
- Detect non-trivial loops (PR [#88](#88)) - Raise a `SPFSyntaxError` exception when an IP address and IP version do not match (PR [#87](#87)) - Fix raising the `DMARCRecordNotFound` exception when a DMARC record does not exist (PR [#86](#86) closes issue [#72](#72)) - Add void lookup limit (PR [#85](#85)) - Add Support for User Defined DNS Resolver Object (PR [#83](#83))
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.
Currently, the parse_spf_record function doesn't detect when a IPv4 Address is written in the
ip6mechanism and the other way round. This MR will fix this behavior.