diff options
| author | Mike Hearn <mike@plan99.net> | 2015-06-19 12:49:40 +0200 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2015-06-19 10:49:48 +0000 |
| commit | 8e30fb284771130f78ff445cd32ce276bb81278b (patch) | |
| tree | 546f93efa5247139c7ff0076613c366a48630e00 | |
| parent | 6058be4b7a5270c8385d60d5f9e0aa8354fac19e (diff) | |
| download | pi-bitcoindev-8e30fb284771130f78ff445cd32ce276bb81278b.tar.gz pi-bitcoindev-8e30fb284771130f78ff445cd32ce276bb81278b.zip | |
Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
| -rw-r--r-- | 69/6e575e356628cb6f35818dc0e1c6bf49cd3d03 | 139 |
1 files changed, 139 insertions, 0 deletions
diff --git a/69/6e575e356628cb6f35818dc0e1c6bf49cd3d03 b/69/6e575e356628cb6f35818dc0e1c6bf49cd3d03 new file mode 100644 index 000000000..8de8d9c02 --- /dev/null +++ b/69/6e575e356628cb6f35818dc0e1c6bf49cd3d03 @@ -0,0 +1,139 @@ +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 <mh.in.england@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>; + 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: <CAEz79PriNzD18Es60=2Nkz5U6G=Ocrm9ezJmK0P1DirdP-vPkw@mail.gmail.com> +References: <CAEz79PoDn+-aDkqSfPeQFUjYDEDEhSrJ2mFYcbitHBf4oADBSg@mail.gmail.com> + <CANEZrP3vut8uYWeeynLdwvSM56eXZZdgidaEgcvg1FNMye6P9w@mail.gmail.com> + <CAEz79Pr4ug8zyJ5bibCG3m0YD8gkBiXysWJsZDThTiwXsgd7YQ@mail.gmail.com> + <CANEZrP1T3r=VDRBTM_jrm_g0BkQy_NZA40BPcZtVDq_0au6TKw@mail.gmail.com> + <CAEz79PriNzD18Es60=2Nkz5U6G=Ocrm9ezJmK0P1DirdP-vPkw@mail.gmail.com> +Date: Fri, 19 Jun 2015 12:49:40 +0200 +X-Google-Sender-Auth: _yEqav0kGtQUXsWvwyLID47DaQw +Message-ID: <CANEZrP30FfSawHFwpf4v1Eg2bHKT7q=hFAaxQhPcMY_eJtCZMQ@mail.gmail.com> +From: Mike Hearn <mike@plan99.net> +To: "Warren Togami Jr." <wtogami@gmail.com> +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 <bitcoin-development@lists.sourceforge.net> +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: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <http://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 + +<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo= +ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left= +-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi= +ng-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmai= +l_quote"><div>Mailman isn't resigning it.=C2=A0 Should it be?=C2=A0 Doe= +s other mailing list software?=C2=A0</div></div></div></div></blockquote><d= +iv><br></div><div>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.</div><div><br></div><div>Yes mailing lists = +that edit people's emails resign. For example, from a recent message to= + the bitcoinj list</div><div><br></div><div><pre style=3D"color:rgb(0,0,0);= +word-wrap:break-word;white-space:pre-wrap">DKIM-Signature: v=3D1; a=3Drsa-s= +ha256; c=3Drelaxed/relaxed; + <b>d=3D<a href=3D"http://googlegroups.com">googlegroups.com</a></b>= +; 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;</pre></div><div>=C2=A0</div><blockquote class= +=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;bo= +rder-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">= +<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><spa= +n><div>I suppose it is somewhat acceptable for us to remove subject tags an= +d footers if we have no choice...<br></div></span></div></div></div></block= +quote><div><br></div><div>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.</div></div></div></div> + +--f46d043bdeda5cf8ab0518dcae5b-- + + |