On 2019/09/17 14:09, Martijn van Duren wrote: > The reason google failed is because my header was named DKIM-signature > instead of DKIM-Signature (note the capital S). Headers are case > insensitive and this is also the case with google, since it does > recognize the header (else we wouldn't have the fail-line). > The problem is that google changes the header-name back to > DKIM-Signature before validating, which is in violation with RFC6376 > section 3.4.1: > Header fields MUST be presented to the signing or verification algorithm > exactly as they are in the message being signed or verified. > > If anyone has a line to the google devs, please let them know.
You could try on the mailops list, but if google has a problem, there's a fair chance other implementations may also have a problem.
