Jump to content

petzl

Memberp
  • Content count

    2,005
  • Joined

  • Last visited

Everything posted by petzl

  1. petzl

    Spamcop cannot find source IP

    Thought I did (2002:a6b:a74f:0:0:0:0:0))? Not sure but if Gmail is nor "arsing" about and would leave it alone forever, SpamCop could have it in as Mailhost overide
  2. petzl

    Spamcop cannot find source IP

    So it is pointy-head junk that does nothing better than the older method in fact seems more inferior way of sorting spam, example had a reply from Microsoft abusse that Gmail (2002:a6b:a74f:0:0:0:0:0) sorted to spam folder, Not impressed, also a lot of Gmail supposed internal IPv6 stamps are gobbledygook I report most spam from my account with Fastmail that use ARC sorting, SpamCop never have problems with parsing them? Gmail seem to be on a death march IMO. No I'm not a mailbox provider or mailing list operator, I just don't like spam! But like spam. I am working on this to me the problem is Gmail, I do like the idea of just reject email that's not set up right. The IP "network" address given by Gmail is gibberish does not specify a IP?
  3. petzl

    Spamcop cannot find source IP

    I get mail from FastMail they use ARC without IPv6 IP's it passes OK? https://www.spamcop.net/sc?id=z6465862542zde0280bc96b77cf07f6a8d426a2f559az
  4. SpamCop stopped reporting reply addresses because most were bogus. However if you think a reply address is a spammers real one you can forward them that email to a AI BOT which starts replying and answering replies of spammers (wastes their time) me [AT ] rescam [ DOT] org
  5. petzl

    Spamcop cannot find source IP

    I suspect ARC if used correctly supposed to delete emails that do not match the sending IP (from domain)? Not intended for sorting The ONLY ones accurate at this (deleting) are CISCO senderbase spam filter that comes with their servers.
  6. petzl

    Spamcop cannot find source IP

    Works if you cut out the supposed and pointless ARC seal. Tracking url below https://www.spamcop.net/sc?id=z6465613809z4fa752930d69a5305d3a14a991008031z
  7. petzl

    Spamcop cannot find source IP

    So is email then
  8. Gmail are stamping headers with network data (ARC) that confuses SpamCop which will fail if any doubt To get SpamCop to parse you have to cut what Gmail call ARC headers to and copy (from) include this line ARC-Authentication-Results: i=1; mx.google.com; past the cut "ARC" in submit notes. "pain in the ARC"
  9. petzl

    Spamcop cannot find source IP

    Not that I can see what ARC headers look like only the claimed Gmail ARC headers that have made zero difference to me getting spam or receiving email but it has made it complicated to report spam
  10. petzl

    Spamcop cannot find source IP

    Not seeing sample headers just more gibber that seems to create more problems than it solves. Pointy-heads who implement bad ideas never set failure terms, in others words cancel a bad idea when its a proved failure (a list of defining failure). Governments are a good example of bad practice keep pouring money into failures. Doubt if Gmail /google care about it's users or SpamCop unless enough turn to another email service. As always "if something is free you are the product"
  11. petzl

    Spamcop cannot find source IP

    What makes you think they are ARC headers? I don't see they are? “spoofing” to me is counterfeit, in this case gibberish, encrypted/coded network headers that only mean something to Google/Gmail spam filtering (a track maybe?) They start and there are a lot of them, just after Delivered-To:X[AT] X [DOT] com? Yes Gmail stamps rhetoric "ARC-Seal" 4 lines down on its network handling/processing. At any rate SpamCop cannot process them. From experience Gmail will disable one's account if spammers cannot be reported and you therefore will get more and more spam going with false positives to Gmails spam folder. Once it hits 20 which was mine Gmail disable the account.
  12. Just some pointy-head idea that Gmail now stamps on top of real received email headers. The gobbledygook explanation I got from Gmail is that it's Gmail's spam from ham sorting header, which may or may not mean something to Gmail but to no one else. I don't think Gmail worries about SpamCop problems, I do know if you don't kill spammers and your spam box gets a "high" quota of spam, Gmail will close your account. SpamCop is the most effective method of killing spammers.
  13. Again, the Gmail ARC headers have nothing to do with finding anything. They are just stamping Gmail gibber that sorts spam from ham through Gmail servers. One has the option to go through the headers and report Gmail spam themselves , or remove the ARC spam headers and feed them into SpamCop. If SpamCop can work out how to ignore these " Gmail ARC headers" yes it would make life easier!
  14. this is nonsensical spam filtering jargon (spoof) that Gmail now adds to it's headers. Has nothing to do with received email headers, then next week Gmail are likely to change it again, The "ARC" filtering has nothing to do with anyone but Gmail. They are not genuine recieved headers.
  15. petzl

    Spamcop cannot find source IP

    Yes this is nonsensical spam filtering jargon (spoof) that Gmail now adds to it's headers. Has nothing to do with received email headers, then next week Gmail are likely to change it again, The "ARC" filtering has nothing to do with anyone but Gmail. They are not genuine recieved headers.
  16. Just get a non-routable Gmail network address? IPv6 Address Report IPv6Address: 2002:ab0:11d9:0:0:0:0:0 AddressType: 2002:AB0:11D9:: 6to4 address Subnet48Id: 0 (/48) InterfaceId: 0:0:0:0 6to4IPv4: 10.176.17.217 Whois: 10.176.17.217
  17. This is becoming a "norm" with Gmail spoofing its own headers? Cut the spoofing out works fine https://www.spamcop.net/sc?id=z6465265014z6d13dd58c97a050619cabd93381ff7f1z
  18. SpamCop has no trouble with IPv6 It is having trouble Gmails spam sorting ARC "headers" which contain a non-routable IPV6
  19. Gmail are getting too smart for their own good! They are stamping their version of ARC rubbish above the real headers! which start at ARC-Authentication-Results: i=1; mx.google.com; Just copy and past into submission include that line SpamCop parses fine . Put what you cut out in notes https://www.spamcop.net/sc?id=z6465051289zf879ca5b6e1b837b8e57756639b0bdc2z
  20. The idea is to try and get better than the Bot SpamCop who can be stupid. Get a Whois program to get real address's, Bottom of page download link http://www.nirsoft.net/utils/ipnetinfo.html often SpamCop gets them wrong, but just reporting get the spam source blocked. Gmail are getting to smart for their own good. if somethings "free" you are the product!
  21. Yes but re-past them in comments
  22. petzl

    spam not recognized as such

    The actual headers start at ARC-Authentication-Results: i=1; mx.google.com; Above that are Gmail Authentication rubbish you need to cut it out parse whats left. THEN past the bit you cut out into notes
  23. Cut the Gmail Authentication headers out you get https://www.spamcop.net/sc?id=z6464905037z91d5435236bd5d8ec7b97204acb1945ez
×