[tahoe-dev] List server leaves invalid DKIM signatures

[Jonathan Dill]

Possibly relevant discussion.

"DKIM has no relation to envelope from. DKIM signs and protects the From:
header (and others). Using envelope from for anything related to DKIM can
only
produce false positives, eg. common forwards."

http://www.gossamer-threads.com/lists/exim/users/93764


On Fri, Nov 8, 2013 at 9:55 AM, Greg Troxel <gdt at ir.bbn.com> wrote:

>
>   DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
>           d=gmail.com; s=20120113;
>
> h=mime-version:in-reply-to:references:date:message-id:subject:from:to
>            :cc:content-type;
>
> Your message (direct to me) had a valid DKIM signature.  It may be that
> DKIM signers should not include the envelope sender.
>
> I tried to take an on-list message and munge the subject back to get
> DKIM to pass but failed.
>
> The standard seems clear, so people can adjust their scores accordingly.
>
> http://tools.ietf.org/html/rfc6377
>
> (Regardless of DKIM, I am opposed to subject munging.  It takes up space
> and provides no value for people with adequate mail setups.)
>
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20131108/d94a4459/attachment.html>