Jump to content

Aunty Spam

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Aunty Spam

  • Rank
  1. Definitely strange because it still doesn't for me. I tried again in case it was a temporary system problem/glitch. http://www.spamcop.net/sc?id=z5455860354ze...6bd941d11ca4cdz
  2. 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 with SMTP id d5csp136869ldg; Sat, 19 Jan 2013 03:47:00 -0800 (PST) X-Received: by 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. []) by mx.google.com with ESMTP id u7si8579741paw.330.2013.; Sat, 19 Jan 2013 03:46:59 -0800 (PST) Received-SPF: pass (google.com: domain of bounce-anon-x123x[at]craigslist.org designates as permitted sender) client-ip=; Authentication-Results: mx.google.com; spf=pass (google.com: domain of bounce-anon-x123x[at]craigslist.org designates as permitted sender) smtp.mail=bounce-anon-x123x[at]craigslist.org Received: from mout.gmx.net (mout.gmx.net []) 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 ([]) 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 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 by rms-us003 with HTTP" but there's still sufficient doubt to not declare it the issue. Cheers.
  3. Aunty Spam

    IPv6 Routing Support

    I too just had an email that SpamCop spit back & said there was no source IP so it couldn't continue: http://www.spamcop.net/sc?id=z5163609103zd...ede547e869ebbdz I think it's tripping over the IPv6 header. I know it skips the 172.x.x.x header (internal IP) and should also ignore the 10.x.x.x IP header as well. The other Received headers seem fine.