Aunty Spam Posted January 19, 2013 Share Posted January 19, 2013 I'm getting a new error that I've never seen before. SC is reporting that there's no date in the email even though it's there as far as I can see in every appropriate header. (I replaced emails w/ x123x). Delivered-To: x123x Received: by 10.114.25.165 with SMTP id d5csp136869ldg; Sat, 19 Jan 2013 03:47:00 -0800 (PST) X-Received: by 10.66.90.34 with SMTP id bt2mr28730687pab.29.1358596019905; Sat, 19 Jan 2013 03:46:59 -0800 (PST) Return-Path: <bounce-anon-x123x[at]craigslist.org> Received: from mxo13f.craigslist.org (mxo13f.craigslist.org. [126.96.36.199]) by mx.google.com with ESMTP id u7si8579741paw.330.2013.01.19.03.46.59; Sat, 19 Jan 2013 03:46:59 -0800 (PST) Received-SPF: pass (google.com: domain of bounce-anon-x123x[at]craigslist.org designates 188.8.131.52 as permitted sender) client-ip=184.108.40.206; Authentication-Results: mx.google.com; spf=pass (google.com: domain of bounce-anon-x123x[at]craigslist.org designates 220.127.116.11 as permitted sender) smtp.mail=bounce-anon-x123x[at]craigslist.org Received: from mout.gmx.net (mout.gmx.net [18.104.22.168]) by craigslist.org (Haraka/1.3.3) with ESMTP id 39838099-C6E4-42EC-8D5F-010D4F63D442.1 (envelope-from <x123x>); Sat, 19 Jan 2013 03:46:44 -0800 Received: from mailout-us.gmx.com ([172.19.198.45]) by mrigmx.server.lan (mrigmxus001) with ESMTP (Nemesis) id 0MbxJK-1TfXjJ25cE-00JFW9 for <x123x>; Sat, 19 Jan 2013 12:46:43 +0100 Received: (qmail 8985 invoked by uid 0); 19 Jan 2013 11:46:43 -0000 Received: from 22.214.171.124 by rms-us003 with HTTP Content-Type: multipart/alternative; boundary="========GMXBoundary125941358596001133520" Date: Sat, 19 Jan 2013 06:46:37 -0500 From: x123x Message-ID: <20130119114641.125940[at]gmx.com> MIME-Version: 1.0 Subject: CRAIGSLIST X-Authenticated: #149463577 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 X-GMX-UID: 9uKIcFZQ3zOl2njBg3whbJ9+IGRvbwC6 X-CL-ID: 39838099-C6E4-42EC-8D5F-010D4F63D442.1 To: undisclosed-recipients:; Any ideas? I suspect this header: "Received: from 126.96.36.199 by rms-us003 with HTTP" but there's still sufficient doubt to not declare it the issue. Cheers. Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.