You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DKIM RFC6376 (https://datatracker.ietf.org/doc/html/rfc6376#section-5.4.1) mentions recommended headers that if present should be signed. It would be great if dkim_verifier could warn about present unsigned recommended headers. For example Subject or Reply-To should be definitely signed.
The text was updated successfully, but these errors were encountered:
Note that this can be configured in the policy options. Would be nice to get feedback on how common warnings in the recommended mode are. I have a few bigger senders that don't sign all headers the RFC recommends, so a little hesitant to make that the default.
The current default relaxed mode only warns about the subject not being signed (from was already an error, as this is a strict requirement in the RFC).
The DKIM RFC6376 (https://datatracker.ietf.org/doc/html/rfc6376#section-5.4.1) mentions recommended headers that if present should be signed. It would be great if dkim_verifier could warn about present unsigned recommended headers. For example Subject or Reply-To should be definitely signed.
The text was updated successfully, but these errors were encountered: