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
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <adam@signal11.com>) id 1Z4aKI-0003PS-5M
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 19:45:46 +0000
X-ACL-Warn:
Received: from mail-qg0-f41.google.com ([209.85.192.41])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z4aKG-0001i1-Cb
for bitcoin-development@lists.sourceforge.net;
Mon, 15 Jun 2015 19:45:46 +0000
Received: by qgeu36 with SMTP id u36so6312630qge.2
for <bitcoin-development@lists.sourceforge.net>;
Mon, 15 Jun 2015 12:45:39 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=No1TAPnHzJpi+FWFQPRlFGg5oJUyvzU8b6GHY73vqVw=;
b=CZ0sLSeg3u9s798Jw2A/EqOhDQBpRAH0BdovIXvlL5OB4Zx/Zxmm9+Bc0J6LE3otOi
gsitLwIdhi/5IKX5BPdotuovzO8MUflcuDw5hxV2Jm5IO+viTWbgFw1R41YFzMwdF3hn
bukzm8FytODlZa5l5Y2aIGbHN9GcYLtNB2XAu3LMjYqRgnWR0JYvVyH1T4H4ixXEc1+0
eTCm6gjrU0LM8XXmLxmlwzTp008nurdeg2PxYrSmxJxhGsvLOyN30qqT77i+db2htA9J
9uMEXTOVpumDpuKCa1W8ZmAJ5KmUHwxl8bCtWlMZf8KTDpanjrg3ofDHP35NtihpS0lm
4ocA==
X-Gm-Message-State: ALoCoQm2qBRius1a8jXf0hyZKHa5Rc0/ORUPwGo+iV9B8iY6ZQQHdPXySdoEB/BxegKpjS8B/TNJ
MIME-Version: 1.0
X-Received: by 10.141.18.136 with SMTP id u130mr38738587qhd.54.1434397538923;
Mon, 15 Jun 2015 12:45:38 -0700 (PDT)
Received: by 10.96.154.66 with HTTP; Mon, 15 Jun 2015 12:45:38 -0700 (PDT)
In-Reply-To: <CANEZrP3uF7AfcH__zHjSUt=RWXG4RfPup=zwnLf_G1_1_oMvmA@mail.gmail.com>
References: <CAEz79Pp_6FhDjtR6emBcXf_WT14MbDaTxMbeAo=QAfhS-ihFCQ@mail.gmail.com>
<CANEZrP3uF7AfcH__zHjSUt=RWXG4RfPup=zwnLf_G1_1_oMvmA@mail.gmail.com>
Date: Mon, 15 Jun 2015 15:45:38 -0400
Message-ID: <CAFVoEQQvs2e8qNDudNb_10UAHfkMEN5JDhG4HaD4Q-CvCKncHg@mail.gmail.com>
From: Adam Weiss <adam@signal11.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: multipart/alternative; boundary=001a113ba98ec64a11051893b3d0
X-Spam-Score: 1.0 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
1.0 HTML_MESSAGE BODY: HTML included in message
X-Headers-End: 1Z4aKG-0001i1-Cb
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 19:45:46 -0000
--001a113ba98ec64a11051893b3d0
Content-Type: text/plain; charset=UTF-8
Recent versions of mailman strip DKIM signatures, rewrite the envelope-from
to use an address at the list's domain and set reply-to to the original
authors address to resolve the DMARC issue. I'm on several lists that do
this and it works just fine.
+1 on moving the list. Given the fact that the mails are archived in
public, it's not really a huge deal how it takes place. One month sounds
reasonable (although I think it could be done on a shorter timescale). I'd
setup the new list to allow subscriptions, but keep it moderated to keep
discussion from moving until the cut, send lots of warnings and then on the
big day unmoderate one and moderate the other.
It's a great opportunity to hardfork something in Bitcoin without risk of
breakage, losses or entertaining melodrama. : )
--adam
ps. I think SF will let project admins download mbox archives of the list,
the new admins should be able to import them to keep archive consistency in
one place.
On Mon, Jun 15, 2015 at 6:13 AM, Mike Hearn <mike@plan99.net> wrote:
> 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!
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--001a113ba98ec64a11051893b3d0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>Recent versions of mailman strip DKIM signatures, rew=
rite the envelope-from to use an address at the list's domain and set r=
eply-to to the original authors address to resolve the DMARC issue.=C2=A0 I=
'm on several lists that do this and it works just fine.<br></div><div>=
<br></div><div>+1 on moving the list.=C2=A0 Given the fact that the mails a=
re archived in public, it's not really a huge deal how it takes place.=
=C2=A0 One month sounds reasonable (although I think it could be done on a =
shorter timescale).=C2=A0 I'd setup the new list to allow subscriptions=
, but keep it moderated to keep discussion from moving until the cut, send =
lots of warnings and then on the big day unmoderate one and moderate the ot=
her.</div><div><br></div><div>It's a great opportunity to hardfork some=
thing in Bitcoin without risk of breakage, losses or entertaining melodrama=
. : )</div><div><br></div><div>--adam</div><div><br></div><div>ps. I think =
SF will let project admins download mbox archives of the list, the new admi=
ns should be able to import them to keep archive consistency in one place.<=
/div><div><br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmai=
l_quote">On Mon, Jun 15, 2015 at 6:13 AM, Mike Hearn <span dir=3D"ltr"><=
<a href=3D"mailto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>>=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div cla=
ss=3D"gmail_extra">Bear in mind the problem that stops Jeff's messages =
getting through is that mailman 1.0 doesn't know how to handle DKIM pro=
perly. Switching to a different mailman provider won'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 from their website. There&=
#39;s a big page on the mailman wiki that suggests they "fixed" i=
t by simply deleting the signatures entirely, which won't work. DMARC p=
olicies state that mail <i>must</i>=C2=A0be signed and unsigned/incorrectly=
signed message should be discarded.</div><div class=3D"gmail_extra"><br></=
div><div class=3D"gmail_extra">The user documentation for mailman 3 doesn&#=
39;t seem to exist? The links on the website are docs for 2.1, perhaps they=
released mailman 3 without refreshing the docs.</div><div class=3D"gmail_e=
xtra"><br></div><div class=3D"gmail_extra">Google Groups may be "contr=
oversial" 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 ju=
st send an email to <a href=3D"mailto:groupname%2Bsubscribe@googlegroups.co=
m" target=3D"_blank">groupname+subscribe@googlegroups.com</a> even if you d=
on'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!</div><div class=3D"gm=
ail_extra"><br></div></div>
<br>-----------------------------------------------------------------------=
-------<br>
<br>_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" rel=3D"noreferrer" target=3D"_blank">https://lists.sourceforge.net/lists/=
listinfo/bitcoin-development</a><br>
<br></blockquote></div><br></div>
--001a113ba98ec64a11051893b3d0--
|
