From: Erik L. <er...@lo...> - 2009-06-24 14:31:12
|
Hi, I noticed that the latest version of dkim-milter uses "x-dkim-adsp" in the AR header instead of dkim-asp. I didn't find any mention of this change in the documentation or a google search. Is x-dkim-adsp part of the new spec thus obsoleting dkim-asp? On a different subject, is there a good way to deal with mailing list software that appends the mailing list name to the "Subject" header? This invalidates the signature, of course, and causes a DKIM failure when it would otherwise pass. I suppose that it's bad practice not not sign the Subject. Regards, Erik. |
From: SM <sm...@re...> - 2009-06-24 15:15:17
|
Hi Erik, At 23:14 23-06-2009, Erik Lotspeich wrote: >I noticed that the latest version of dkim-milter uses "x-dkim-adsp" in >the AR header instead of dkim-asp. I didn't find any mention of this >change in the documentation or a google search. Is x-dkim-adsp part of >the new spec thus obsoleting dkim-asp? dkim-adsp is not in the email authentication result name registry defined in RFC 5451. That's why x-dkim-adsp is used in the latest version of dkim-milter. The "x-" denotes that x-dkim-adsp is for private use as it doesn't have a registration. >On a different subject, is there a good way to deal with mailing list >software that appends the mailing list name to the "Subject" header? >This invalidates the signature, of course, and causes a DKIM failure >when it would otherwise pass. I suppose that it's bad practice not not >sign the Subject. I won't recommend not signing the "Subject" header. You can use the "z=" tag to reconstruct the "Subject" header. Some mailing lists also modify the body of the message. You could use the "l=" tag if the lines have been appended to get back the original body that was signed. Regards, -sm |