Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1YqOQt-0007kw-3M
	for bitcoin-development@lists.sourceforge.net;
	Thu, 07 May 2015 16:13:55 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.175 as permitted sender)
	client-ip=209.85.212.175; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f175.google.com; 
Received: from mail-wi0-f175.google.com ([209.85.212.175])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1YqOQs-0006kk-36
	for bitcoin-development@lists.sourceforge.net;
	Thu, 07 May 2015 16:13:55 +0000
Received: by widdi4 with SMTP id di4so65977052wid.0
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 07 May 2015 09:13:48 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.61.82 with SMTP id n18mr8568937wjr.35.1431015228100;
	Thu, 07 May 2015 09:13:48 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.194.90.114 with HTTP; Thu, 7 May 2015 09:13:47 -0700 (PDT)
In-Reply-To: <CAJHLa0NTuKX7NWM6cuvSgaDnLqiZ-0+CyBE5nwV0SpCRziwkDQ@mail.gmail.com>
References: <554A91BE.6060105@bluematt.me>
	<CAJHLa0NTuKX7NWM6cuvSgaDnLqiZ-0+CyBE5nwV0SpCRziwkDQ@mail.gmail.com>
Date: Thu, 7 May 2015 18:13:47 +0200
X-Google-Sender-Auth: D7i__YFwc4wggV6obmpbjNEOSOc
Message-ID: <CANEZrP3yU+sZxtxwK55pD9f_tuwDNuSF8Y3SVzRfqE6k9gJzvQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=047d7ba9778057a5190515803209
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: 1YqOQs-0006kk-36
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
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: Thu, 07 May 2015 16:13:55 -0000

--047d7ba9778057a5190515803209
Content-Type: text/plain; charset=UTF-8

>
> Dear list,
>
> Apparently my emails are being marked as spam, despite being sent from
> GMail's web interface.  I've pinged our sysadmin.


It's a problem with the mailing list software, not your setup. BitPay could
disable the phishing protections but that seems like a poor solution. The
only real fix is to send from a non @bitpay.com email address. Gmail or
Hotmail will work, I think. Yahoo won't: they enforce the same strict
policies than bitpay does.

--047d7ba9778057a5190515803209
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">Dear list,<br>
<br>
Apparently my emails are being marked as spam, despite being sent from<br>
GMail&#39;s web interface.=C2=A0 I&#39;ve pinged our sysadmin.</blockquote>=
<div><br></div><div>It&#39;s a problem with the mailing list software, not =
your setup. BitPay could disable the phishing protections but that seems li=
ke a poor solution. The only real fix is to send from a non @<a href=3D"htt=
p://bitpay.com">bitpay.com</a> email address. Gmail or Hotmail will work, I=
 think. Yahoo won&#39;t: they enforce the same strict policies than bitpay =
does.</div></div></div></div>

--047d7ba9778057a5190515803209--