Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Z5trn-0007TE-WA for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 10:49:48 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.182 as permitted sender) client-ip=209.85.212.182; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f182.google.com; Received: from mail-wi0-f182.google.com ([209.85.212.182]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Z5trm-0006r9-OQ for bitcoin-development@lists.sourceforge.net; Fri, 19 Jun 2015 10:49:47 +0000 Received: by wibee9 with SMTP id ee9so5798853wib.0 for ; Fri, 19 Jun 2015 03:49:40 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.181.11.193 with SMTP id ek1mr5440356wid.15.1434710980751; Fri, 19 Jun 2015 03:49:40 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.28.14.196 with HTTP; Fri, 19 Jun 2015 03:49:40 -0700 (PDT) In-Reply-To: References: Date: Fri, 19 Jun 2015 12:49:40 +0200 X-Google-Sender-Auth: _yEqav0kGtQUXsWvwyLID47DaQw Message-ID: From: Mike Hearn To: "Warren Togami Jr." Content-Type: multipart/alternative; boundary=f46d043bdeda5cf8ab0518dcae5b X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Z5trm-0006r9-OQ Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Mailman incompatibility with DKIM ... X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jun 2015 10:49:48 -0000 --f46d043bdeda5cf8ab0518dcae5b Content-Type: text/plain; charset=UTF-8 > > Mailman isn't resigning it. Should it be? Does other mailing list > software? > Mailman must take responsibility for the mail itself. It doesn't have to actually sign with DKIM to do so: for backwards compatibility, spam filters fall back to other heuristics to try and figure out the 'owner' of the mail if it doesn't use DKIM. Those heuristics can go wrong of course. Ideally all mail would be DKIM signed. There's no reason not to do it, really. Yes mailing lists that edit people's emails resign. For example, from a recent message to the bitcoinj list DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; *d=googlegroups.com *; s=20120806; h=to:from:subject:date:lines:message-id:references:mime-version :content-type:user-agent:in-reply-to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-subscribe :list-unsubscribe; > I suppose it is somewhat acceptable for us to remove subject tags and > footers if we have no choice... > Good email clients can extract the same information from the headers anyway. I filter all my mail based on them, and the headers also contain unsubscribe instructions. Gmail is capable of using them programmatically. --f46d043bdeda5cf8ab0518dcae5b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Mailman isn't resigning it.=C2=A0 Should it be?=C2=A0 Doe= s other mailing list software?=C2=A0

Mailman must take responsibility for the mail itself. It = doesn't have to actually sign with DKIM to do so: for backwards compati= bility, spam filters fall back to other heuristics to try and figure out th= e 'owner' of the mail if it doesn't use DKIM. Those heuristics = can go wrong of course. Ideally all mail would be DKIM signed. There's = no reason not to do it, really.

Yes mailing lists = that edit people's emails resign. For example, from a recent message to= the bitcoinj list

DKIM-Signature: v=3D1; a=3Drsa-s=
ha256; c=3Drelaxed/relaxed;
        d=3Dgooglegroups.com=
; s=3D20120806;
        h=3Dto:from:subject:date:lines:message-id:references:mime-version
         :content-type:user-agent:in-reply-to:x-original-sender
         :x-original-authentication-results:reply-to:precedence:mailing-lis=
t
         :list-id:list-post:list-help:list-archive:sender:list-subscribe
         :list-unsubscribe;
=C2=A0
=
I suppose it is somewhat acceptable for us to remove subject tags an= d footers if we have no choice...

Good email clients can extract the same informati= on from the headers anyway. I filter all my mail based on them, and the hea= ders also contain unsubscribe instructions. Gmail is capable of using them = programmatically.
--f46d043bdeda5cf8ab0518dcae5b--