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
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <rodney.morris@gmail.com>) id 1Wc7JE-0005Rw-DC
for bitcoin-development@lists.sourceforge.net;
Mon, 21 Apr 2014 06:02:28 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.160.44 as permitted sender)
client-ip=209.85.160.44; envelope-from=rodney.morris@gmail.com;
helo=mail-pb0-f44.google.com;
Received: from mail-pb0-f44.google.com ([209.85.160.44])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Wc7JD-0004Vu-Hq
for bitcoin-development@lists.sourceforge.net;
Mon, 21 Apr 2014 06:02:28 +0000
Received: by mail-pb0-f44.google.com with SMTP id rp16so3405898pbb.31
for <bitcoin-development@lists.sourceforge.net>;
Sun, 20 Apr 2014 23:02:21 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.66.191.134 with SMTP id gy6mr36017448pac.27.1398060141664;
Sun, 20 Apr 2014 23:02:21 -0700 (PDT)
Received: by 10.70.134.6 with HTTP; Sun, 20 Apr 2014 23:02:21 -0700 (PDT)
Received: by 10.70.134.6 with HTTP; Sun, 20 Apr 2014 23:02:21 -0700 (PDT)
In-Reply-To: <CA+s+GJAgEOWvuTDdpU8N11-YtmRrtfb2E=WYmQrOFd0LybDWYw@mail.gmail.com>
References: <CABerxhEbsVC6MWU_KGjvMBOaN9JbDj5S1PZmxYwAsJN-SiOAmw@mail.gmail.com>
<CA+s+GJAgEOWvuTDdpU8N11-YtmRrtfb2E=WYmQrOFd0LybDWYw@mail.gmail.com>
Date: Mon, 21 Apr 2014 16:02:21 +1000
Message-ID: <CABerxhHrvdOSthcD9aLb+sjcMZ5+4pFM_ihBY5xiBQfwt9Do9w@mail.gmail.com>
From: Rodney Morris <rodney.morris@gmail.com>
To: Wladimir <laanwj@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bdc7f741e63eb04f7873e5e
X-Spam-Score: -0.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
(rodney.morris[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Wc7JD-0004Vu-Hq
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Mailing list abuse
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: Mon, 21 Apr 2014 06:02:28 -0000
--047d7bdc7f741e63eb04f7873e5e
Content-Type: text/plain; charset=UTF-8
Not a bad idea. Semantics of the word abuse not withstanding.
I don't want to become the self appointed mailing list cop, but I notice it
maybe more than others because I almost exclusively read this mailing list
on a mobile device. Hence my asking for feedback without publicly calling
anyone out.
Thanks for taking the time to reply.
Rodney
On 21/04/2014 3:47 pm, "Wladimir" <laanwj@gmail.com> wrote:
> On Mon, Apr 21, 2014 at 6:58 AM, Rodney Morris <rodney.morris@gmail.com>
> wrote:
> > What is the procedure for dealing with it? Is it considered abuse to
> reply
> > to and quote the entire digest for the sake of a few lines of content?
> Am I
> > the only one annoyed by this (if so I'll just shut right up).
>
> I would not go as far as calling it 'abuse' if it is not done on
> purpose. Probably the person doesn't even know he/she is doing this.
> Best to mail the person and ask (nicely) instead of complaining to the
> list.
>
> Wladimir
>
--047d7bdc7f741e63eb04f7873e5e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<p dir=3D"ltr">Not a bad idea. Semantics of the word abuse not withstanding=
.</p>
<p dir=3D"ltr">I don't want to become the self appointed mailing list c=
op, but I notice it maybe more than others because I almost exclusively rea=
d this mailing list on a mobile device. Hence my asking for feedback withou=
t publicly calling anyone out. </p>
<p dir=3D"ltr">Thanks for taking the time to reply. </p>
<p dir=3D"ltr">Rodney <br>
</p>
<div class=3D"gmail_quote">On 21/04/2014 3:47 pm, "Wladimir" <=
<a href=3D"mailto:laanwj@gmail.com">laanwj@gmail.com</a>> wrote:<br type=
=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">
On Mon, Apr 21, 2014 at 6:58 AM, Rodney Morris <<a href=3D"mailto:rodney=
.morris@gmail.com">rodney.morris@gmail.com</a>> wrote:<br>
> What is the procedure for dealing with it? Is it considered abuse to r=
eply<br>
> to and quote the entire digest for the sake of a few lines of content?=
Am I<br>
> the only one annoyed by this (if so I'll just shut right up).<br>
<br>
I would not go as far as calling it 'abuse' if it is not done on<br=
>
purpose. Probably the person doesn't even know he/she is doing this.<br=
>
Best to mail the person and ask (nicely) instead of complaining to the<br>
list.<br>
<br>
Wladimir<br>
</blockquote></div>
--047d7bdc7f741e63eb04f7873e5e--
|
