summaryrefslogtreecommitdiff
path: root/eb/d6e29f2bda6f00e3a3d145de5d5ee3c664e16a
blob: f715f5c423552762e9d5339c175427d608e01090 (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
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 <elombrozo@gmail.com>) id 1RdKhG-0006fT-8p
	for bitcoin-development@lists.sourceforge.net;
	Wed, 21 Dec 2011 11:50:58 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.220.175 as permitted sender)
	client-ip=209.85.220.175; envelope-from=elombrozo@gmail.com;
	helo=mail-vx0-f175.google.com; 
Received: from mail-vx0-f175.google.com ([209.85.220.175])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1RdKhA-0001Pt-Nm
	for bitcoin-development@lists.sourceforge.net;
	Wed, 21 Dec 2011 11:50:58 +0000
Received: by vcbf1 with SMTP id f1so6562827vcb.34
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 21 Dec 2011 03:50:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.70.167 with SMTP id n7mr3451700vdu.67.1324468247312; Wed,
	21 Dec 2011 03:50:47 -0800 (PST)
Received: by 10.52.162.6 with HTTP; Wed, 21 Dec 2011 03:50:47 -0800 (PST)
Date: Wed, 21 Dec 2011 03:50:47 -0800
Message-ID: <CABr1YTf_s06Z4QgWLOSwjznLPrbGGVRk0=DxKTcGs6t6MZcMFw@mail.gmail.com>
From: Eric Lombrozo <elombrozo@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
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
	(elombrozo[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
	0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RdKhA-0001Pt-Nm
Subject: [Bitcoin-development] Why are my posts being put in new threads?
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, 21 Dec 2011 11:50:58 -0000

I've made a couple recent posts that were intended for the Protocol
extensions thread but have been put in new threads. What part of the
email message is used to identify the thread to which it belongs? I
would have thought the subject, but apparently it isn't.