Closed erolkskn closed 9 months ago
Indeed, the RFC referenced is incorrect! Good catch.
(Ref b8ad33f365217742ff7ed5e38abb5afbb88944c7)
RFC 6376 section 6.1.1 actually is about the DKIM-Signature header field, not about the TXT record.
RFC 6376 section 3.6 explains that the v
field is optional.
Indeed, the RFC referenced is incorrect! Good catch.
(Ref b8ad33f)
RFC 6376 section 6.1.1 actually is about the DKIM-Signature header field, not about the TXT record.
RFC 6376 section 3.6 explains that the
v
field is optional.
Oops I misread that section title. Thank you for implementing this :-)
Hi,
Some of the providers doesn't include v tag on DKIM record as it wasn't specified as required in older versions of DKIM standard. It would be great if it was optional or fallback to
DKIM1
if nov
tag was specified on TXT record.Here are some of the examples of DKIM records without v tag:
Sendgrid:
GitLab:
Note: https://github.com/emersion/go-msgauth/blob/6610fd7f91288877b3982a4ac9647291e9d99b23/dkim/query.go#L91 This requirement is actually stated in
RFC 6376 6.1.1
not inRFC 7489 6.6.3
as this RFC is about DMARC records not DKIM. https://datatracker.ietf.org/doc/html/rfc6376#section-6.1.1