opendkim-ar: Accept AR header with a no-result as valid syntax.#205
Open
futatuki wants to merge 2 commits intotrusteddomainproject:developfrom
Open
opendkim-ar: Accept AR header with a no-result as valid syntax.#205futatuki wants to merge 2 commits intotrusteddomainproject:developfrom
futatuki wants to merge 2 commits intotrusteddomainproject:developfrom
Conversation
futatuki
added a commit
to futatuki/OpenDKIM
that referenced
this pull request
Mar 13, 2024
futatuki
added a commit
to futatuki/OpenDKIM
that referenced
this pull request
Apr 26, 2024
…-result opendkim-ar: Accept AR header with a no-result as a valid syntax.
futatuki
added a commit
to futatuki/OpenDKIM
that referenced
this pull request
Apr 26, 2024
futatuki
added a commit
to futatuki/OpenDKIM
that referenced
this pull request
Jun 21, 2024
…r-no-result fix comment in opendkim/opendkim-ar.c:ares_parse()
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
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.
Current parser for Authentication header does not accept the case that
authres-payload containsno-resultin RFC8601 section 2.2.This is a fix for it.