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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gmaxwell@gmail.com>) id 1Y2RbG-0003Fo-Im
for bitcoin-development@lists.sourceforge.net;
Sat, 20 Dec 2014 21:30:10 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.175 as permitted sender)
client-ip=209.85.223.175; envelope-from=gmaxwell@gmail.com;
helo=mail-ie0-f175.google.com;
Received: from mail-ie0-f175.google.com ([209.85.223.175])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Y2RbF-00054G-7o
for bitcoin-development@lists.sourceforge.net;
Sat, 20 Dec 2014 21:30:10 +0000
Received: by mail-ie0-f175.google.com with SMTP id x19so2503251ier.6
for <bitcoin-development@lists.sourceforge.net>;
Sat, 20 Dec 2014 13:30:04 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.107.138.5 with SMTP id m5mr13984806iod.85.1419111003899;
Sat, 20 Dec 2014 13:30:03 -0800 (PST)
Received: by 10.107.16.30 with HTTP; Sat, 20 Dec 2014 13:30:03 -0800 (PST)
In-Reply-To: <op.xq5yue2cyldrnw@laptop-air>
References: <CAB2qGxXDtxWxyLUCEZ9XQ4nP0U-Cj5Xiz9ac=vot1H+wzRCHrA@mail.gmail.com>
<54953A11.1060202@bluematt.me>
<20141220100816.GD7902@giles.gnomon.org.uk>
<op.xq5yue2cyldrnw@laptop-air>
Date: Sat, 20 Dec 2014 21:30:03 +0000
Message-ID: <CAAS2fgRB33c+JGphkT72OiRnLY_41b5Ufkfmff=4u-yB1oq2Qw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Jeremy Spilman <jeremy@taplink.co>
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
(gmaxwell[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: 1Y2RbF-00054G-7o
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Area of Focus
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: Sat, 20 Dec 2014 21:30:10 -0000
On Sat, Dec 20, 2014 at 11:14 AM, Jeremy Spilman <jeremy@taplink.co> wrote:
>> are dnsseeds being blocked
> ostensibly because they are acting as dyanamic DNS infrastructure for
> malware sites?
Pretty much appears to be the case. In every instance it appears to be
automated. This predates the msft no-ip.com stuff.
We also had similar problems with the IRC based method that the
software originally used.
It's the same story for mail relay spam blacklisting. There is a
whole industry out there selling people semi-snake-oil blocking
solutions to make the baddness of the internet go away. The low margin
business demands a cheap and highly automated approach... lots of
inappropriate things get blocked. Nagging people to fix things is time
consuming, better to move out of their sights a bit, so that they at
least have to specifically target Bitcoin. If they do, it'll at least
be worth the time spent fixing it.
I believe opendns is blocking all of sipa.be still as we speak, so if
you'd like to see it for yourself try to load http://bitcoin.sipa.be
while using opendns.
|
