blob: 1c8d249a5d3d3d5865e1693026bfddff2e275701 (
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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <grarpamp@gmail.com>) id 1SPrza-000270-NW
for bitcoin-development@lists.sourceforge.net;
Thu, 03 May 2012 09:06:30 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.181 as permitted sender)
client-ip=209.85.212.181; envelope-from=grarpamp@gmail.com;
helo=mail-wi0-f181.google.com;
Received: from mail-wi0-f181.google.com ([209.85.212.181])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SPrzV-0004jJ-DC
for bitcoin-development@lists.sourceforge.net;
Thu, 03 May 2012 09:06:30 +0000
Received: by wibhr17 with SMTP id hr17so114924wib.10
for <bitcoin-development@lists.sourceforge.net>;
Thu, 03 May 2012 02:06:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.180.105.198 with SMTP id go6mr1252856wib.19.1336035979209;
Thu, 03 May 2012 02:06:19 -0700 (PDT)
Received: by 10.180.106.229 with HTTP; Thu, 3 May 2012 02:06:19 -0700 (PDT)
In-Reply-To: <CA+8xBpczLTCzikGr62K-4paxecOTtcxFPygQsp7JRg_0DwvMEQ@mail.gmail.com>
References: <1335808239.18613.YahooMailNeo@web121006.mail.ne1.yahoo.com>
<201205020931.01718.luke@dashjr.org>
<CAD2Ti2_AUG7zmhwrg1GK9iDOgAh5RNrSEGvJefWCc0Uo=-GQbw@mail.gmail.com>
<201205021230.46349.luke@dashjr.org>
<CAD2Ti29NGc7F1_w5VgKm565CXwhrFPZvMx4BgE_5PVbh0SYU5w@mail.gmail.com>
<CA+8xBpczLTCzikGr62K-4paxecOTtcxFPygQsp7JRg_0DwvMEQ@mail.gmail.com>
Date: Thu, 3 May 2012 05:06:19 -0400
Message-ID: <CAD2Ti2_AFj34yZY-7PVc66XbMahr0MwHOMk8AsHQvFncpcee6A@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: Jeff Garzik <jgarzik@exmulti.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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
(grarpamp[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
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: 1SPrzV-0004jJ-DC
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] new bitcoin.org clients page
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: Thu, 03 May 2012 09:06:30 -0000
> "Reply-To" Munging Considered Harmful
> http://www.unicom.com/pw/reply-to-harmful.html
Ok, ok. but only because this reminds me of the
top-posting and formatting advice page that
I can't seem to find right now.
But I'm not munging what my client decides to
put in to/cc on a g reply either :)
|
