From mboxrd@z Thu Jan 1 00:00:00 1970 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 ) 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 ; 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: References: <54953A11.1060202@bluematt.me> <20141220100816.GD7902@giles.gnomon.org.uk> Date: Sat, 20 Dec 2014 21:30:03 +0000 Message-ID: From: Gregory Maxwell To: Jeremy Spilman 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 Subject: Re: [Bitcoin-development] Area of Focus X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Dec 2014 21:30:10 -0000 On Sat, Dec 20, 2014 at 11:14 AM, Jeremy Spilman 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.