Re: AlwaysSignHeaders results in "fail"

From: <lutz.niederer_at_gmx.net>
Date: Tue, 19 Jun 2012 00:47:34 +0200

> On Mon, 18 Jun 2012, lutz.niederer_at_gmx.net wrote:
> > Taken from dkim.c v2.0.1:
> >
> > /* recommended list of headers to sign, from RFC4871 section 5.5 */
> > const u_char *dkim_should_signhdrs[] =
> > {
> > "from",
> > [...]
>
> That list is from RFC4871. RFC6376 is current and the list is shorter.
> But generally, you're on the right track.

If you say "better go for the short list" then I will use the short list from the new RFC. Would there be anything else I have to change if I should use the short list or is SignHeaders the only option I have to change to make 2.0.1 aware of the new RFC?

-lutzn


-- 
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!                                  
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
Received on Mon Jun 18 2012 - 22:47:50 PST

This archive was generated by hypermail 2.3.0 : Mon Oct 29 2012 - 23:20:40 PST