Ian Kelling <[email protected]> writes:

> The relevant option dkim_sign_headers is unspecified.
>
> https://www.exim.org/exim-html-current/doc/html/spec_html/ch-support_for_dkim_domainkeys_identified_mail.html
> says in that case, "the header names recommended in RFC4871 will be
> used"
>
> https://www.ietf.org/rfc/rfc4871.txt:
> "header fields SHOULD be included in the signature, if
>    they are present in the message being signed:"
>    
> My signature looks to have all RFC4871 headers, but my message
> definitely does not have them:
>
> h=Date:Message-Id:Subject:To:From:Sender:Reply-To:Cc:
>       MIME-Version:Content-Type:Content-Transfer-Encoding:Content-ID:
>       
> Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc
>       
> :Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:
>       List-Subscribe:List-Post:List-Owner:List-Archive
>
> I'm testing with exim 4.89-6 from debian.
>
> Should this be happening? How can I make exim only sign headers that are
> in the message I send? Thanks in advance.

Well, I found my answer that this is intentional. I've filed a bug
https://bugs.exim.org/show_bug.cgi?id=2179

- Ian

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Reply via email to