summaryrefslogtreecommitdiff
path: root/b8/15e2610949d343e53e2b7639bdd11ae4ed34d9
blob: 64d3b6dda1190b9b12c652e4ce2016cc7cc9201f (plain)
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
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
Return-Path: <info@AndySchroder.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id C3281323
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 23 Jun 2015 18:52:11 +0000 (UTC)
X-Greylist: delayed 00:07:05 by SQLgrey-1.7.6
Received: from uschroder.com (uschroder.com [74.142.93.202])
	by smtp1.linuxfoundation.org (Postfix) with ESMTP id 958CB191
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Tue, 23 Jun 2015 18:52:10 +0000 (UTC)
Received: from [192.168.253.4] (cpe-74-132-161-228.kya.res.rr.com
	[74.132.161.228])
	by uschroder.com (Postfix) with ESMTPSA id 75FB022E2CF4F;
	Tue, 23 Jun 2015 14:45:05 -0400 (EDT)
Message-ID: <5589A92D.5050902@AndySchroder.com>
Date: Tue, 23 Jun 2015 14:45:01 -0400
From: Andy Schroder <info@AndySchroder.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Warren Togami Jr." <wtogami@gmail.com>
References: <CAEz79Po7irWrCEfgoRqsLxgwY+R1=cZae5z7NrHJfxM9iBro5g@mail.gmail.com>
In-Reply-To: <CAEz79Po7irWrCEfgoRqsLxgwY+R1=cZae5z7NrHJfxM9iBro5g@mail.gmail.com>
X-Enigmail-Version: 1.6
OpenPGP: id=2D44186B;
	url=http://andyschroder.com/static/AndySchroder.asc
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="7XQgjuJOLrrmogqMIJ382tksXA0duF0jx"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Welcome to the new Bitcoin Dev List
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jun 2015 18:52:11 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7XQgjuJOLrrmogqMIJ382tksXA0duF0jx
Content-Type: multipart/alternative;
 boundary="------------010105080007060702040507"

This is a multi-part message in MIME format.
--------------010105080007060702040507
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Hello,

I'm not sure if anyone has submitted a request for gmane to monitor and=20
archive this new list, but I did. Maybe it's not best for many people to =

re-request that? For those who aren't aware, gmane has a nice HTTP/HTML=20
archive as well as a newsgroup proxy that is also very nice for reading=20
the archive. They'll also subscribe the list to mail-archive.com for you.=


I've also noticed that gmane=20
(http://dir.gmane.org/gmane.comp.bitcoin.devel) does not have exactly=20
the same archive for the old bitcoin-development list=20
(http://sourceforge.net/p/bitcoin/mailman/bitcoin-development/). It's=20
missing a few months at the beginning. The new list archive does contain =

the same thing as the old list=20
(https://lists.linuxfoundation.org/pipermail/bitcoin-dev/).

gmane has an option to import old archives, so I'm seeing if they can do =

that with the https://lists.linuxfoundation.org/pipermail/bitcoin-dev/=20
list, since it is complete. In order to avoid confusion on what list is=20
the most complete, if they can, I may request them delete or rename=20
their old, incomplete archive at=20
http://dir.gmane.org/gmane.comp.bitcoin.devel . It's possible they could =

even make this new list use that same name after deleting or renaming=20
that old archive.


There is also bitcoin-list=20
(http://sourceforge.net/p/bitcoin/mailman/bitcoin-list/). I think that=20
one may be discontinued? That list appears to be older and contains some =

of Satoshi's original e-mails. On gmane though=20
(http://dir.gmane.org/gmane.comp.bitcoin.user), it is missing the first=20
few years of archives. Do we want to try and preserve this historical=20
correspondence on any way before sourceforce disappears?




Regarding message footers and the subject prefix of [bitcoin-dev], it=20
would be cool if mailman allowed people to change this on a per-user basi=
s.

Andy Schroder

On 06/21/2015 05:29 PM, Warren Togami Jr. wrote:
> Hi folks,
>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> The move is now complete.  The previous archive has been fully=20
> imported and new posts here will now be saved.
>
> *Greylisting Notice*
> Your first post to this list may be delayed by 5+ minutes due to=20
> Greylisting <https://en.wikipedia.org/wiki/Greylisting>. Subsequent=20
> posts should go through without delay. Contact Freenode #bitcoin-dev=20
> if you have any questions or concerns.
>
> *TODO*
>
>   * LF will be upgrading Mailman soon to better handle posts from DKIM
>     enforced domains.
>   * There will be a few more config tweaks like auto-rejecting
>     non-subscribed posts.  Nobody has time to moderate this list, and
>     mail silently disappearing into the moderation hold blackhole is
>     worse than an instant reject message telling people to subscribe.
>     Unfortunately, it is too dangerous to auto-reject spam ... those
>     messages need to go into a blackhole to prevent bounce abuse.
>
> Warren Togami
>
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


--------------010105080007060702040507
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DISO-8859-1"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">Hello,<br>
      <br>
      I'm not sure if anyone has submitted a request for gmane to
      monitor and archive this new list, but I did. Maybe it's not best
      for many people to re-request that? For those who aren't aware,
      gmane has a nice HTTP/HTML archive as well as a newsgroup proxy
      that is also very nice for reading the archive. They'll also
      subscribe the list to mail-archive.com for you.<br>
      <br>
      I've also noticed that gmane
      (<a class=3D"moz-txt-link-freetext" href=3D"http://dir.gmane.org/gm=
ane.comp.bitcoin.devel">http://dir.gmane.org/gmane.comp.bitcoin.devel</a>=
) does not have
      exactly the same archive for the old bitcoin-development list
      (<a class=3D"moz-txt-link-freetext" href=3D"http://sourceforge.net/=
p/bitcoin/mailman/bitcoin-development/">http://sourceforge.net/p/bitcoin/=
mailman/bitcoin-development/</a>).
      It's missing a few months at the beginning. The new list archive
      does contain the same thing as the old list
      (<a class=3D"moz-txt-link-freetext" href=3D"https://lists.linuxfoun=
dation.org/pipermail/bitcoin-dev/">https://lists.linuxfoundation.org/pipe=
rmail/bitcoin-dev/</a>).<br>
      <br>
      gmane has an option to import old archives, so I'm seeing if they
      can do that with the
      <a class=3D"moz-txt-link-freetext" href=3D"https://lists.linuxfound=
ation.org/pipermail/bitcoin-dev/">https://lists.linuxfoundation.org/piper=
mail/bitcoin-dev/</a> list,
      since it is complete. In order to avoid confusion on what list is
      the most complete, if they can, I may request them delete or
      rename their old, incomplete archive at
      <a class=3D"moz-txt-link-freetext" href=3D"http://dir.gmane.org/gma=
ne.comp.bitcoin.devel">http://dir.gmane.org/gmane.comp.bitcoin.devel</a> =
=2E It's possible they
      could even make this new list use that same name after deleting or
      renaming that old archive.<br>
      <br>
      <br>
      There is also bitcoin-list
      (<a class=3D"moz-txt-link-freetext" href=3D"http://sourceforge.net/=
p/bitcoin/mailman/bitcoin-list/">http://sourceforge.net/p/bitcoin/mailman=
/bitcoin-list/</a>). I think
      that one may be discontinued? That list appears to be older and
      contains some of Satoshi's original e-mails. On gmane though
      (<a class=3D"moz-txt-link-freetext" href=3D"http://dir.gmane.org/gm=
ane.comp.bitcoin.user">http://dir.gmane.org/gmane.comp.bitcoin.user</a>),=
 it is missing the
      first few years of archives. Do we want to try and preserve this
      historical correspondence on any way before sourceforce
      disappears?<br>
      <br>
      <br>
      <br>
      <br>
      Regarding message footers and the subject prefix of [bitcoin-dev],
      it would be cool if mailman allowed people to change this on a
      per-user basis.<br>
      <br>
      <pre class=3D"moz-signature" cols=3D"72">Andy Schroder</pre>
      On 06/21/2015 05:29 PM, Warren Togami Jr. wrote:<br>
    </div>
    <blockquote
cite=3D"mid:CAEz79Po7irWrCEfgoRqsLxgwY+R1=3DcZae5z7NrHJfxM9iBro5g@mail.gm=
ail.com"
      type=3D"cite">
      <div dir=3D"ltr">
        <div>Hi folks,</div>
        <div><br>
        </div>
        <a moz-do-not-send=3D"true"
          href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitc=
oin-dev">https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev</=
a><br>
        <div>The move is now complete.&nbsp; The previous archive has bee=
n
          fully imported and new posts here will now be saved.</div>
        <div><br>
        </div>
        <div><b style=3D"color:rgb(0,0,0);font-family:'Times New
            Roman';font-size:medium">Greylisting Notice</b><span
            style=3D"color:rgb(0,0,0);font-family:'Times New
            Roman';font-size:medium">&nbsp;</span><br
            style=3D"color:rgb(0,0,0);font-family:'Times New
            Roman';font-size:medium">
          <span style=3D"color:rgb(0,0,0);font-family:'Times New
            Roman';font-size:medium">Your first post to this list may be
            delayed by 5+ minutes due to&nbsp;</span><a
            moz-do-not-send=3D"true"
            href=3D"https://en.wikipedia.org/wiki/Greylisting"
            style=3D"font-family:'Times New Roman';font-size:medium">Grey=
listing</a><span
            style=3D"color:rgb(0,0,0);font-family:'Times New
            Roman';font-size:medium">. Subsequent posts should go
            through without delay. Contact Freenode #bitcoin-dev if you
            have any questions or concerns.</span><br>
        </div>
        <div><br>
        </div>
        <div><b>TODO</b></div>
        <div>
          <ul>
            <li>LF will be upgrading Mailman soon to better handle posts
              from DKIM enforced domains.</li>
            <li>There will be a few more config tweaks like
              auto-rejecting non-subscribed posts.&nbsp; Nobody has time =
to
              moderate this list, and mail silently disappearing into
              the moderation hold blackhole is worse than an instant
              reject message telling people to subscribe. &nbsp;
              Unfortunately, it is too dangerous to auto-reject spam ...
              those messages need to go into a blackhole to prevent
              bounce abuse.</li>
          </ul>
          Warren Togami&nbsp;<br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
bitcoin-dev mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:bitcoin-dev@lists.li=
nuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.linuxfoundation.=
org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailm=
an/listinfo/bitcoin-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------010105080007060702040507--

--7XQgjuJOLrrmogqMIJ382tksXA0duF0jx
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJViakuAAoJEDT679stRBhrFncIAID2TW9gSeSLc4r9beAWDYAj
z7ZvIxWQwraXhYsmjJDC03RAuecoAHnA1pWcCi+yQ6NeDEfp8H64ZTV65ZUJVuXo
GPx1pWCEs0dMpzpdb/dAogIpUFCuAPtpqd/UlSJ+scDgfrOO3T9Sm2RACEtXbGDr
jO58o8+eka24oiTxzEmZ6leEIZAD8HcuycXukWGFX6WhgkCjOjZVEtbA3lBo/WRy
tEQL07nMu14vnStE5D+Zx20A22rG80ElE2R/Wrgji4u3Mh9l7YrCeYNjIlMsoNHx
GgfBstOrJD/6p4DsHDcCa1EanW22sMhIF8xwnI7GwgCbxSKGrVuP67xMTaYph7M=
=isay
-----END PGP SIGNATURE-----

--7XQgjuJOLrrmogqMIJ382tksXA0duF0jx--