Incomplete AAR header is generated if there is no own AR header. #174
Comments
futatuki
added a commit
to futatuki/OpenARC
that referenced
this issue
Sep 11, 2024
… no own AR header
This was referenced Sep 11, 2024
futatuki
added a commit
to futatuki/OpenARC
that referenced
this issue
Sep 16, 2024
…x-aar-no-result Fix issue trusteddomainproject#174: incomplete AAR header if there is no own AR header trusteddomainproject#174 trusteddomainproject#176
flowerysong
added a commit
to flowerysong/OpenARC
that referenced
this issue
Oct 2, 2024
It is not valid to have no authentication results; if no message authentication was performed the special value no-result (`[CFWS] ";" [CFWS] "none"`) should be used. trusteddomainproject/OpenARC#174
futatuki
pushed a commit
to futatuki/OpenARC
that referenced
this issue
Oct 3, 2024
It is not valid to have no authentication results; if no message authentication was performed the special value no-result (`[CFWS] ";" [CFWS] "none"`) should be used. trusteddomainproject#174
futatuki
pushed a commit
to futatuki/OpenARC
that referenced
this issue
Oct 3, 2024
It is not valid to have no authentication results; if no message authentication was performed the special value no-result (`[CFWS] ";" [CFWS] "none"`) should be used. trusteddomainproject#174
60 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In signing mode, if a message does not have Authentication-Results: header with same authserve-id, openarc milter generates incomplete ARC-Authentication-Results: header such as:
According to RFC8601 Section 2.2, authres-payload should have at least one res info or exact one no-result. So the above should be:
The text was updated successfully, but these errors were encountered: