4c694a9c171032bcba318f672a04258fa22850
1 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] 2 helo=mx.sourceforge.net) 3 by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) 4 (envelope-from <grarpamp@gmail.com>) id 1SPrza-000270-NW 5 for bitcoin-development@lists.sourceforge.net; 6 Thu, 03 May 2012 09:06:30 +0000 7 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com 8 designates 209.85.212.181 as permitted sender) 9 client-ip=209.85.212.181; envelope-from=grarpamp@gmail.com; 10 helo=mail-wi0-f181.google.com; 11 Received: from mail-wi0-f181.google.com ([209.85.212.181]) 12 by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) 13 (Exim 4.76) id 1SPrzV-0004jJ-DC 14 for bitcoin-development@lists.sourceforge.net; 15 Thu, 03 May 2012 09:06:30 +0000 16 Received: by wibhr17 with SMTP id hr17so114924wib.10 17 for <bitcoin-development@lists.sourceforge.net>; 18 Thu, 03 May 2012 02:06:19 -0700 (PDT) 19 MIME-Version: 1.0 20 Received: by 10.180.105.198 with SMTP id go6mr1252856wib.19.1336035979209; 21 Thu, 03 May 2012 02:06:19 -0700 (PDT) 22 Received: by 10.180.106.229 with HTTP; Thu, 3 May 2012 02:06:19 -0700 (PDT) 23 In-Reply-To: <CA+8xBpczLTCzikGr62K-4paxecOTtcxFPygQsp7JRg_0DwvMEQ@mail.gmail.com> 24 References: <1335808239.18613.YahooMailNeo@web121006.mail.ne1.yahoo.com> 25 <201205020931.01718.luke@dashjr.org> 26 <CAD2Ti2_AUG7zmhwrg1GK9iDOgAh5RNrSEGvJefWCc0Uo=-GQbw@mail.gmail.com> 27 <201205021230.46349.luke@dashjr.org> 28 <CAD2Ti29NGc7F1_w5VgKm565CXwhrFPZvMx4BgE_5PVbh0SYU5w@mail.gmail.com> 29 <CA+8xBpczLTCzikGr62K-4paxecOTtcxFPygQsp7JRg_0DwvMEQ@mail.gmail.com> 30 Date: Thu, 3 May 2012 05:06:19 -0400 31 Message-ID: <CAD2Ti2_AFj34yZY-7PVc66XbMahr0MwHOMk8AsHQvFncpcee6A@mail.gmail.com> 32 From: grarpamp <grarpamp@gmail.com> 33 To: Jeff Garzik <jgarzik@exmulti.com> 34 Content-Type: text/plain; charset=UTF-8 35 X-Spam-Score: -1.6 (-) 36 X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. 37 See http://spamassassin.org/tag/ for more details. 38 -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for 39 sender-domain 40 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider 41 (grarpamp[at]gmail.com) 42 -0.0 SPF_PASS SPF: sender matches SPF record 43 -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from 44 author's domain 45 0.1 DKIM_SIGNED Message has a DKIM or DK signature, 46 not necessarily valid 47 -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 48 X-Headers-End: 1SPrzV-0004jJ-DC 49 Cc: bitcoin-development@lists.sourceforge.net 50 Subject: Re: [Bitcoin-development] new bitcoin.org clients page 51 X-BeenThere: bitcoin-development@lists.sourceforge.net 52 X-Mailman-Version: 2.1.9 53 Precedence: list 54 List-Id: <bitcoin-development.lists.sourceforge.net> 55 List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, 56 <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> 57 List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> 58 List-Post: <mailto:bitcoin-development@lists.sourceforge.net> 59 List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> 60 List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, 61 <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> 62 X-List-Received-Date: Thu, 03 May 2012 09:06:30 -0000 63 64 > "Reply-To" Munging Considered Harmful 65 > http://www.unicom.com/pw/reply-to-harmful.html 66 67 Ok, ok. but only because this reminds me of the 68 top-posting and formatting advice page that 69 I can't seem to find right now. 70 71 But I'm not munging what my client decides to 72 put in to/cc on a g reply either :) 73 74