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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1W31VV-0000Jq-BR
for bitcoin-development@lists.sourceforge.net;
Tue, 14 Jan 2014 10:46:05 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.219.54 as permitted sender)
client-ip=209.85.219.54; envelope-from=mh.in.england@gmail.com;
helo=mail-oa0-f54.google.com;
Received: from mail-oa0-f54.google.com ([209.85.219.54])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1W31VU-0004W3-Mp
for bitcoin-development@lists.sourceforge.net;
Tue, 14 Jan 2014 10:46:05 +0000
Received: by mail-oa0-f54.google.com with SMTP id o6so9552941oag.27
for <bitcoin-development@lists.sourceforge.net>;
Tue, 14 Jan 2014 02:45:59 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.182.143.103 with SMTP id sd7mr524663obb.70.1389696359356;
Tue, 14 Jan 2014 02:45:59 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.76.99.112 with HTTP; Tue, 14 Jan 2014 02:45:59 -0800 (PST)
In-Reply-To: <lb30mu$jjh$1@ger.gmane.org>
References: <CAPg+sBhdgVQvumL_r9thLD5wm7UOJx=2DE+01-T58HHdimvpXw@mail.gmail.com>
<lb18l6$nu2$1@ger.gmane.org>
<CAPg+sBji5sFWZ_mDVXKKwkyeGYDbLmvwau457nmntT_NgTT+Sw@mail.gmail.com>
<lb30mu$jjh$1@ger.gmane.org>
Date: Tue, 14 Jan 2014 11:45:59 +0100
X-Google-Sender-Auth: Luov3QXjtoajW-Y2g3FFp-hPBjA
Message-ID: <CANEZrP3BeFMLtcThr=Gp5mudbtQeT_dHno1DGQzOg28YKBNkzA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andreas Schildbach <andreas@schildbach.de>
Content-Type: multipart/alternative; boundary=e89a8ff1ce9ed85f6904efebe5ab
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: 1W31VU-0004W3-Mp
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Payment protocol and reliable Payment
messages
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: Tue, 14 Jan 2014 10:46:05 -0000
--e89a8ff1ce9ed85f6904efebe5ab
Content-Type: text/plain; charset=UTF-8
>
> Imagine you get a good offer (payment request) from a merchant. You
> would like to accept that offer, however the merchant has changed his
> mind.
Usually if the merchant has not delivered, then at that point it's not a
problem and he is allowed to change his mind. It's only if they change
their mind *after* you pay that it's a problem, right?
--e89a8ff1ce9ed85f6904efebe5ab
Content-Type: text/html; charset=UTF-8
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Imagine you get a good offer (payment request) from a merchant. You<br>
would like to accept that offer, however the merchant has changed his<br>
mind.</blockquote><div><br></div><div>Usually if the merchant has not delivered, then at that point it's not a problem and he is allowed to change his mind. It's only if they change their mind *after* you pay that it's a problem, right?</div>
</div></div></div>
--e89a8ff1ce9ed85f6904efebe5ab--
|
