Jump to content

styncer

Members
  • Content Count

    3
  • Joined

  • Last visited

Everything posted by styncer

  1. From my experience, Gmail is adding a header line "Bcc: <email@domain.com>" if the message was only sent with you in the "Bcc" field. This header is added at the bottom of the headers below the "Content-Type:". This breaks the SpamCop parser. If I move the Bcc line above the Content-Type line, SpamCop is able to parse the message properly. Is this similar to what you see? How does one report a bug in SpamCop's parser?
  2. I've been reporting spam using spamcop.net for years. A few weeks ago, all of the spam that I receive through my @icloud.com address is no longer able to be processed by spamcop. I receive the error, "Mailhost configuration problem, identified internal IP as source" and cannot proceed. I typically post the email source into the online form. I've tried using the email submission as well ... no change. Here are the top headers of the email I just received (with my account removed) Return-path: <bounce@sansat.online> Original-recipient: rfc822;*******@icloud.com Received: from st42p59im-ztdg12250601 by st42p59ic-ztdg12240101 (mailgateway 1922B206) with SMTP id 183f8e09-ae71-4b00-baa3-458a228427ab for <*******@icloud.com>; Wed, 4 Dec 2019 22:57:59 GMT Received: from 17.36.65.61 by 17.36.65.25 (mailnotify 1916B19:12:18:22:57:59:60); Wed, 4 Dec 2019 22:57:59 GMT X-Apple-MoveToFolder: Junk (36) uid 12 user ******* modseq 0 X-Apple-Action: JUNK/Junk X-Apple-UUID: 183f8e09-ae71-4b00-baa3-458a228427ab Received: from ip21.ip-178-32-48.eu (ip21.ip-178-32-48.eu [178.32.48.21]) by pv33p00im-smtpin029.me.com (Postfix) with ESMTPS id 4845BAA00C2 for <*******@icloud.com>; Wed, 4 Dec 2019 22:57:56 +0000 (UTC) Would someone please offer a suggestion for how I can get this to work again?
  3. I apologize for the delay in my response. I've tried to follow the Add Mailhost for my address (*****@mac.com) again. I receive the test email, and when I paste the headers and body into the form, it returns the following error: When I try to follow the "Proceed Here" URL, I receive an error, "500 Internal Server Error".
×