#14 case-sensitive verification of header field names

[Eijiro Sumii]

I have installed dkimproxy-1.0.1 on my server, but verification fails when I send a message like below, because one of the MTAs (on which I have no control) rewrites "cc:" to "Cc:". I am not sure who is "wrong" with respect to RFCs, but case-insensitive verification of head filed names seems more reasonable to me.

Message-Id: <20080212.104550.21591998.sumii@example.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: xxx
From: Eijiro Sumii <sumii@example.com>
To: somebody@example.com
cc: sumii@example.com
Date: Tue, 12 Feb 2008 10:45:50 +0900 (JST)
X-Mailer: Mew version 5.1 on Emacs 21.3 / Mule 5.0 (SAKAKI)

yyyyy

[Eijiro Sumii]

Logged In: YES
user_id=30536
Originator: YES

P.S. I filed my report here after reading http://www.meulie.net/portal_plugins/forum/forum_viewtopic.php?9193, but I noticed nobody else (other than Jason himself:-) has reported anything so far. Sorry if it was out of place.

[Jason Long]

I think if you use the "relaxed" canonicalization method, the message will still be valid even after the downstream MTA rewrites 'cc' to 'Cc'.

Otherwise, there's nothing DKIMproxy can do differently. In this respect it can only do according to the DKIM specification (RFC 4871).