Bitcoin Forum

https://i.imgur.com/gTF9cws.png


Delivered-To: xxxxx@gmail.com
Received: by 10.140.84.42 with SMTP id k39csp83154qgd;
        Mon, 27 Jan 2014 07:39:29 -0800 (PST)
X-Received: by 10.236.17.34 with SMTP id i22mr551691yhi.110.1390837169733;
        Mon, 27 Jan 2014 07:39:29 -0800 (PST)
Return-Path: <contact@coinbase.com>
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net. [209.86.89.65])
        by mx.google.com with ESMTP id s22si8938905yha.176.2014.01.27.07.39.29
        for <xxxxx@gmail.com>;
        Mon, 27 Jan 2014 07:39:29 -0800 (PST)
Received-SPF: fail (google.com: domain of contact@coinbase.com does not designate 209.86.89.65 as permitted sender) client-ip=209.86.89.65;
Authentication-Results: mx.google.com;
       spf=hardfail (google.com: domain of contact@coinbase.com does not designate 209.86.89.65 as permitted sender) smtp.mail=contact@coinbase.com;
       dmarc=fail (p=NONE dis=NONE) header.from=coinbase.com
Received: from [208.94.99.214] (helo=SuperMailer-User)
   by elasmtp-kukur.atl.sa.earthlink.net with esmtpa (Exim 4.67)
   (envelope-from <contact@coinbase.com>)
   id 1W7oGM-0006NN-K5
   for xxxxxx@gmail.com; Mon, 27 Jan 2014 10:38:14 -0500
From: "Coinbase" <contact@coinbase.com>
Subject: BTC Sent
To: xxxxxx@gmail.com
Content-Type: multipart/alternative; boundary="2YXC3d=_LDwc6ZArZtfkLh5134uGXluOWB"
MIME-Version: 1.0
Date: Mon, 27 Jan 2014 10:38:11 -0500
Message-Id: <20140127103810F13A409C47$23468BFBD8@localhost>
X-ELNK-Trace: 88be657e1447a7311aa676d7e74259b7b3291a7d08dfec79fbcb726aa5ff9179f25b79370093cd5 7350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 208.94.99.214


Check Transaction Status http://goo.gl/short-link-to-malware

Thanks for the heads up. :)