1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
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 1XeT4Z-0002kk-9t
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Oct 2014 18:13:19 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.218.44 as permitted sender)
client-ip=209.85.218.44; envelope-from=mh.in.england@gmail.com;
helo=mail-oi0-f44.google.com;
Received: from mail-oi0-f44.google.com ([209.85.218.44])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1XeT4X-0007tm-1J
for bitcoin-development@lists.sourceforge.net;
Wed, 15 Oct 2014 18:13:19 +0000
Received: by mail-oi0-f44.google.com with SMTP id x69so1409413oia.17
for <bitcoin-development@lists.sourceforge.net>;
Wed, 15 Oct 2014 11:13:11 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.202.6.142 with SMTP id 136mr11864274oig.34.1413396791517;
Wed, 15 Oct 2014 11:13:11 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.86.105 with HTTP; Wed, 15 Oct 2014 11:13:11 -0700 (PDT)
In-Reply-To: <CALqxMTErVtN2bj7s=DiX4ajzMtQ=M+_DCFQ0=jT6QWUVaXwY_w@mail.gmail.com>
References: <CA+s+GJCAWXgpzyQnAar6ecKdcci+tdR8yJjCOUpB=xmj-ytZZQ@mail.gmail.com>
<CABsx9T1U10R4t9NNO9rSSfBxcpOLQNvKFC=7fRKa5Tq41+67cQ@mail.gmail.com>
<CANEZrP1yFOWcJUr+ML73Eoqa=EvYRZivkogdrFdww+5QsOXhBw@mail.gmail.com>
<CALqxMTErVtN2bj7s=DiX4ajzMtQ=M+_DCFQ0=jT6QWUVaXwY_w@mail.gmail.com>
Date: Wed, 15 Oct 2014 20:13:11 +0200
X-Google-Sender-Auth: DlbiiqK9scGImybEUVx9Z3SJff4
Message-ID: <CANEZrP0-Rnoe2GzvTs4nztbTMWKVxxuW=qMMwtcgoQJCvRkosA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Adam Back <adam@cypherspace.org>
Content-Type: multipart/alternative; boundary=001a113d1300af688805057a1541
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: 1XeT4X-0007tm-1J
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] BIP process
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: Wed, 15 Oct 2014 18:13:19 -0000
--001a113d1300af688805057a1541
Content-Type: text/plain; charset=UTF-8
I don't care much what exact list software/service is used, but lists.sf.net
hasn't changed in years and is basically dying. Trashing all @yahoo
accounts because ancient mailman does a MITM attack on people's email is no
good, it's not any better than a web proxy that breaks every SSL
connection. For a project that is based on digital signatures, it's really
bad that the mailing list is incompatible with Yahoo's "mail signatures
must be valid" policy.
Plus its moderation features suck, its mail archiving features suck, etc.
It essentially has no redeeming features at all.
mail-archive.com can be easily used with any mailing list, so not sure why
that's brought up. You just add it as a member, as documented here:
http://www.mail-archive.com/faq.html#newlist
--001a113d1300af688805057a1541
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">I don't care much what exact list software/service is =
used, but <a href=3D"http://lists.sf.net">lists.sf.net</a> hasn't chang=
ed in years and is basically dying. Trashing all @yahoo accounts because an=
cient mailman does a MITM attack on people's email is no good, it's=
not any better than a web proxy that breaks every SSL connection.=C2=A0For=
a project that is based on digital signatures, it's really bad that th=
e mailing list is incompatible with Yahoo's "mail signatures must =
be valid" policy.<div><br></div><div>Plus its=C2=A0moderation features=
suck, its mail archiving features suck, etc. It essentially has no redeemi=
ng features at all.</div><div><br></div><div><a href=3D"http://mail-archive=
.com">mail-archive.com</a> can be easily used with any mailing list, so not=
sure why that's brought up. You just add it as a member, as documented=
here:=C2=A0<a href=3D"http://www.mail-archive.com/faq.html#newlist">http:/=
/www.mail-archive.com/faq.html#newlist</a><br><div><br></div><div><br></div=
></div></div>
--001a113d1300af688805057a1541--
|
