/ 15 / 11087eb5513c702a5aa174bb20fe4f55c77db1
11087eb5513c702a5aa174bb20fe4f55c77db1
 1  Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
 2  	helo=mx.sourceforge.net)
 3  	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
 4  	(envelope-from <rmckay@gmail.com>) id 1QiGqg-0000Nl-HV
 5  	for bitcoin-development@lists.sourceforge.net;
 6  	Sun, 17 Jul 2011 02:12:50 +0000
 7  Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
 8  	designates 209.85.212.47 as permitted sender)
 9  	client-ip=209.85.212.47; envelope-from=rmckay@gmail.com;
10  	helo=mail-vw0-f47.google.com; 
11  Received: from mail-vw0-f47.google.com ([209.85.212.47])
12  	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
13  	(Exim 4.76) id 1QiGqe-0006Uu-W8
14  	for bitcoin-development@lists.sourceforge.net;
15  	Sun, 17 Jul 2011 02:12:50 +0000
16  Received: by vws2 with SMTP id 2so2373223vws.34
17  	for <bitcoin-development@lists.sourceforge.net>;
18  	Sat, 16 Jul 2011 19:12:43 -0700 (PDT)
19  MIME-Version: 1.0
20  Received: by 10.52.177.101 with SMTP id cp5mr5064359vdc.343.1310868762285;
21  	Sat, 16 Jul 2011 19:12:42 -0700 (PDT)
22  Sender: rmckay@gmail.com
23  Received: by 10.52.184.202 with HTTP; Sat, 16 Jul 2011 19:12:42 -0700 (PDT)
24  In-Reply-To: <CA+8xBpf-xrmz3Eo7ZjitUHivR1fU4gRZt_1mdi=1EDrOLpZmVw@mail.gmail.com>
25  References: <CAJNQ0stPb+3yarKh4M+tFpjSaSG4-GrZX9AVFPh5q7+Ho_OJOA@mail.gmail.com>
26  	<1310813679.2195.0.camel@Desktop666>
27  	<CAJNQ0st1hv4k-11EHOPDqkkXCGQh41ysKhUmT6qgLu8uaGng=Q@mail.gmail.com>
28  	<CAJNQ0svFL6JMpcRNyJ=xpv0wrn1EpGOUG7ff2-JXH5BKJVHZqQ@mail.gmail.com>
29  	<CA+8xBpduc=vn_Q7Kw0m+VkuHjz0FTxjDZB+hOPLnRJcuh49gJw@mail.gmail.com>
30  	<83816D44-004A-43C4-AFFE-ED1BABD90144@jrbobdobbs.org>
31  	<CA+8xBpf-xrmz3Eo7ZjitUHivR1fU4gRZt_1mdi=1EDrOLpZmVw@mail.gmail.com>
32  Date: Sun, 17 Jul 2011 03:12:42 +0100
33  X-Google-Sender-Auth: RRy1ww3GvBY8d7gnEEBr2wXHGSE
34  Message-ID: <CAAqW1RE9MfUFb4quwtvX+BNhx7ream6yiSQGuQt1KSPMXyipUQ@mail.gmail.com>
35  From: Robert McKay <robert@mckay.com>
36  To: Jeff Garzik <jgarzik@exmulti.com>
37  Content-Type: text/plain; charset=ISO-8859-1
38  X-Spam-Score: -1.5 (-)
39  X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
40  	See http://spamassassin.org/tag/ for more details.
41  	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
42  	sender-domain
43  	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
44  	(rmckay[at]gmail.com)
45  	-0.0 SPF_PASS               SPF: sender matches SPF record
46  	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
47  	not necessarily valid
48  	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
49  X-Headers-End: 1QiGqe-0006Uu-W8
50  Cc: bitcoin-development@lists.sourceforge.net
51  Subject: Re: [Bitcoin-development] The forums...
52  X-BeenThere: bitcoin-development@lists.sourceforge.net
53  X-Mailman-Version: 2.1.9
54  Precedence: list
55  List-Id: <bitcoin-development.lists.sourceforge.net>
56  List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
57  	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
58  List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
59  List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
60  List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
61  List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
62  	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
63  X-List-Received-Date: Sun, 17 Jul 2011 02:12:50 -0000
64  
65  On 7/17/11, Jeff Garzik <jgarzik@exmulti.com> wrote:
66  > On Sat, Jul 16, 2011 at 9:16 PM, Douglas Huff <dhuff@jrbobdobbs.org> wrote:
67  >> I say just kill the forum.bitcoin.org DNS entry along with it.
68  >
69  > Hopefully sirius will do this when he moves forum.bitcoin.org to
70  > forum.bitcointalk.org.
71  >
72  > But sirius is the only one with keys to bitcoin.org DNS, so....
73  
74  At the risk of making myself very unpopular, perhaps it's the
75  development project that should move to a new URL?
76  
77  Rob
78  
79