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
104
105
106
107
108
109
110
111
112
113
114
|
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 1Z4ROd-0003fj-Fm
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 10:13:39 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 74.125.82.42 as permitted sender)
client-ip=74.125.82.42; envelope-from=mh.in.england@gmail.com;
helo=mail-wg0-f42.google.com;
Received: from mail-wg0-f42.google.com ([74.125.82.42])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z4ROc-0000N0-F9
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 10:13:39 +0000
Received: by wgbhy7 with SMTP id hy7so31494329wgb.2
for <bitcoin-development@lists.sourceforge.net>;
Mon, 15 Jun 2015 03:13:32 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.181.11.193 with SMTP id ek1mr30098565wid.15.1434363212501;
Mon, 15 Jun 2015 03:13:32 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.28.14.196 with HTTP; Mon, 15 Jun 2015 03:13:32 -0700 (PDT)
In-Reply-To: <CAEz79Pp_6FhDjtR6emBcXf_WT14MbDaTxMbeAo=QAfhS-ihFCQ@mail.gmail.com>
References: <CAEz79Pp_6FhDjtR6emBcXf_WT14MbDaTxMbeAo=QAfhS-ihFCQ@mail.gmail.com>
Date: Mon, 15 Jun 2015 12:13:32 +0200
X-Google-Sender-Auth: MYpJSYCxbWvBGUH8j6nkIRH1ISs
Message-ID: <CANEZrP3uF7AfcH__zHjSUt=RWXG4RfPup=zwnLf_G1_1_oMvmA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: "Warren Togami Jr." <wtogami@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043bdedac2986f05188bb5d8
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: 1Z4ROc-0000N0-F9
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Proposal: Move Bitcoin Dev List to a
Neutral Competent Entity
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: Mon, 15 Jun 2015 10:13:39 -0000
--f46d043bdedac2986f05188bb5d8
Content-Type: text/plain; charset=UTF-8
Bear in mind the problem that stops Jeff's messages getting through is that
mailman 1.0 doesn't know how to handle DKIM properly. Switching to a
different mailman provider won't fix that.
Does mailman 3.0 even fix this? I found it difficult to tell from their
website. There's a big page on the mailman wiki that suggests they "fixed"
it by simply deleting the signatures entirely, which won't work. DMARC
policies state that mail *must* be signed and unsigned/incorrectly signed
message should be discarded.
The user documentation for mailman 3 doesn't seem to exist? The links on
the website are docs for 2.1, perhaps they released mailman 3 without
refreshing the docs.
Google Groups may be "controversial" but if I recall correctly the main
issue was the question of whether you needed a Google account or not. I'm
pretty sure you can just send an email to
groupname+subscribe@googlegroups.com even if you don't have a Google
account. But of course this is a bizarre standard to hold mailing list
software to: mailman asks users to create an account for each listserv in
order to manage a subscription too!
--f46d043bdedac2986f05188bb5d8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra">Bear in mind the problem that s=
tops Jeff's messages getting through is that mailman 1.0 doesn't kn=
ow how to handle DKIM properly. Switching to a different mailman provider w=
on't fix that.</div><div class=3D"gmail_extra"><br></div><div class=3D"=
gmail_extra">Does mailman 3.0 even fix this? I found it difficult to tell f=
rom their website. There's a big page on the mailman wiki that suggests=
they "fixed" it by simply deleting the signatures entirely, whic=
h won't work. DMARC policies state that mail <i>must</i>=C2=A0be signed=
and unsigned/incorrectly signed message should be discarded.</div><div cla=
ss=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The user documentat=
ion for mailman 3 doesn't seem to exist? The links on the website are d=
ocs for 2.1, perhaps they released mailman 3 without refreshing the docs.</=
div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Google =
Groups may be "controversial" but if I recall correctly the main =
issue was the question of whether you needed a Google account or not. I'=
;m pretty sure you can just send an email to <a href=3D"mailto:groupname%2B=
subscribe@googlegroups.com">groupname+subscribe@googlegroups.com</a> even i=
f you don't have a Google account. But of course this is a bizarre stan=
dard to hold mailing list software to: mailman asks users to create an acco=
unt for each listserv in order to manage a subscription too!</div><div clas=
s=3D"gmail_extra"><br></div></div>
--f46d043bdedac2986f05188bb5d8--
|
