Jump to content


  • Posts

  • Joined

  • Last visited

ChuckGary61's Achievements


Newbie (1/6)



  1. yup, you keep klunging I'll keep munging, friend. just a little copy/paste isn't that big a hassle. but I would rather SpamCop would parse all spam correctly, since I'm paying for it. But maybe not for much longer...
  2. ... so I'll keep munging the headers from Gmail spam.
  3. parenthesis being handshake-kosher or not, Hotmail spam with IPv6 format works! "Received: from AM5EUR02HT112.eop-EUR02.prod.protection.outlook.com (2603:10a6:3:cf::25) by HE1PR03MB1338.eurprd03.prod.outlook.com with HTTPS via HE1P191CA0015.EURP191.PROD.OUTLOOK.COM; Sat, 23 Jun 2018 13:10:24 +0000" parses correctly as: Report spam to: Re: 2603:10a6:3:cf:0:0:0:25 (Administrator of network where email originates) To: report_spam@hotmail.com (Notes) so WHY doesn't Gmail's IPv6 header spam work? munging headers seems to be much less "kosher", IMO!
  4. "Sorry, there is a problem This attachment is not available. It may have been removed or the person who shared it may not have permission to share it to this location. Error code: 2C171/1" That's what that link turns up to me.
  5. I just copy/paste the ipv6 into a whois, then copy/paste the resulting ipv4, replacing the ipv6 in the headers - yes it's munging, but it works and like RobieBue says, it amounts to ripping the "ipv6 disguise" off, so in my view, a legit munging. Curiously Hotmail doesn't have this problem, since it puts the ipv6 into a parenthesis that somehow, the spamcop parser ignores, and thus parses correctly. Again, Spamcop should provide a workaround, like they did for "eudora users" - why not one for "gmail users", Spamcop?
  6. I was beginning to think SPAMMERS had found a new way to fool the spamcop parser! If spam assumes new formats, spamcop - a paid service - should include adaptations or instructions on how to go around these issues. Thank you RobieBue, this worked like a charm.
  • Create New...