summaryrefslogtreecommitdiff
path: root/96/2e8f291980b547f197ef75d436571b5d06cc88
blob: 05cfeb29554a6d6f99ffdcbc912f7c7a33fd347d (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
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	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 1XeQmK-00042Y-DO
	for bitcoin-development@lists.sourceforge.net;
	Wed, 15 Oct 2014 15:46:20 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.174 as permitted sender)
	client-ip=209.85.214.174; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f174.google.com; 
Received: from mail-ob0-f174.google.com ([209.85.214.174])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1XeQmJ-0004e7-BB
	for bitcoin-development@lists.sourceforge.net;
	Wed, 15 Oct 2014 15:46:20 +0000
Received: by mail-ob0-f174.google.com with SMTP id wp18so1247511obc.19
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 15 Oct 2014 08:46:13 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.103.41 with SMTP id ft9mr11500213oeb.14.1413387973859;
	Wed, 15 Oct 2014 08:46:13 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.86.105 with HTTP; Wed, 15 Oct 2014 08:46:13 -0700 (PDT)
In-Reply-To: <CABsx9T1U10R4t9NNO9rSSfBxcpOLQNvKFC=7fRKa5Tq41+67cQ@mail.gmail.com>
References: <CA+s+GJCAWXgpzyQnAar6ecKdcci+tdR8yJjCOUpB=xmj-ytZZQ@mail.gmail.com>
	<CABsx9T1U10R4t9NNO9rSSfBxcpOLQNvKFC=7fRKa5Tq41+67cQ@mail.gmail.com>
Date: Wed, 15 Oct 2014 17:46:13 +0200
X-Google-Sender-Auth: mOy6veNRIT1dkZbkV4QDc-vFCck
Message-ID: <CANEZrP1yFOWcJUr+ML73Eoqa=EvYRZivkogdrFdww+5QsOXhBw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: multipart/alternative; boundary=089e0118400a1ca28c05057808f9
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: 1XeQmJ-0004e7-BB
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 15:46:20 -0000

--089e0118400a1ca28c05057808f9
Content-Type: text/plain; charset=UTF-8

>
> Great idea. Jeff Garzik was looking for a better mailing list solution
> than SourceForge, but assuming
> there isn't a clearly better solution I think "we" should create a
> strictly moderated bitcoin-bips@lists.sourceforge list.
>

Let's stay away from SF.net or any mailman-controlled lists if at all
possible. They break DKIM signatures which means they're no longer
compatible with Yahoo, all mail from Yahoo users gets spamfoldered
immediately. Google Groups gets this right. Perhaps other list operators do
too. Groups also has moderation features.

--089e0118400a1ca28c05057808f9
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"><div><div class=3D"gmail_extra"=
>Great idea. Jeff Garzik was looking for a better mailing list solution tha=
n SourceForge, but assuming</div><div class=3D"gmail_extra">there isn&#39;t=
 a clearly better solution I think &quot;we&quot; should create a strictly =
moderated bitcoin-bips@lists.sourceforge list.</div></div></div></blockquot=
e><div><br></div><div>Let&#39;s stay away from SF.net or any mailman-contro=
lled lists if at all possible. They break DKIM signatures which means they&=
#39;re no longer compatible with Yahoo, all mail from Yahoo users gets spam=
foldered immediately. Google Groups gets this right. Perhaps other list ope=
rators do too. Groups also has moderation features.</div></div></div></div>

--089e0118400a1ca28c05057808f9--