Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.174 as permitted sender)
	client-ip=209.85.212.174; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f174.google.com; 
MIME-Version: 1.0
Sender: mh.in.england@gmail.com
In-Reply-To: <CAEz79PoDn+-aDkqSfPeQFUjYDEDEhSrJ2mFYcbitHBf4oADBSg@mail.gmail.com>
References: <CAEz79PoDn+-aDkqSfPeQFUjYDEDEhSrJ2mFYcbitHBf4oADBSg@mail.gmail.com>
Date: Fri, 19 Jun 2015 11:56:16 +0200
Message-ID: <CANEZrP3vut8uYWeeynLdwvSM56eXZZdgidaEgcvg1FNMye6P9w@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: "Warren Togami Jr." <wtogami@gmail.com>
Content-Type: multipart/alternative; boundary=047d7ba978a05ee7240518dbef29
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
Precedence: list

--047d7ba978a05ee7240518dbef29
Content-Type: text/plain; charset=UTF-8

>
> We already removed the footer because it was incompatible with DKIM
> signing.  Keeping the "[Bitcoin-dev] " prepend tag in subject is compatible
> with DKIM header signing only if the poster manually prepends it in their
> subject header.
>

I still see footers being added to this list by SourceForge?


> Opinions?
>

I've asked Jeff to not use his @bitpay.com account for now.

The only real fix is to use a mailing list operator that is designed to
operate correctly with DKIM/DMARC, either by not modifying messages in
transit, or by re-sending (and ideally re-signing) under their own identity.

Though I'm sure this won't be an issue for the Linux Foundation, the latter
approach is dangerous because it means the list operator takes full
responsibility for any spamming that occurs from that domain. If the mail
server is ever hacked or spammers start posting to the lists themselves,
all that spam will be seen as originating from the listserv itself and the
reputation will be degraded. It can end with everyone's mail going to the
spam folder.

--047d7ba978a05ee7240518dbef29
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:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div dir=3D"ltr">We already removed the footer b=
ecause it was incompatible with DKIM signing.=C2=A0 Keeping the &quot;[Bitc=
oin-dev] &quot; prepend tag in subject is compatible with DKIM header signi=
ng only if the poster manually prepends it in their subject header.</div></=
blockquote><div><br></div><div>I still see footers being added to this list=
 by SourceForge?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
dir=3D"ltr"><div>Opinions?<br></div></div></blockquote><div><br></div><div>=
I&#39;ve asked Jeff to not use his @<a href=3D"http://bitpay.com">bitpay.co=
m</a> account for now.</div><div><br></div><div>The only real fix is to use=
 a mailing list operator that is designed to operate correctly with DKIM/DM=
ARC, either by not modifying messages in transit, or by re-sending (and ide=
ally re-signing) under their own identity.</div><div><br></div><div>Though =
I&#39;m sure this won&#39;t be an issue for the Linux Foundation, the latte=
r approach is dangerous because it means the list operator takes full respo=
nsibility for any spamming that occurs from that domain. If the mail server=
 is ever hacked or spammers start posting to the lists themselves, all that=
 spam will be seen as originating from the listserv itself and the reputati=
on will be degraded. It can end with everyone&#39;s mail going to the spam =
folder.</div><div><br></div></div></div></div>

--047d7ba978a05ee7240518dbef29--