Jump to content

petzl

Memberp
  • Content Count

    2,400
  • Joined

  • Last visited

Everything posted by petzl

  1. petzl

    Spams received already outdated

    When some email server or Botnet starts spewing spam, occasionally they are taken offline. but when started up again it finishes the out of date spew! When you parse spam at top of page before you submit there is a tracking URL posting this, one can look up IP's to see when spam was happening and when it stopped and if it restarts For instance 35.182.184.76 couple of sites I use to check, was a Botnet, but it now seems a malware scan was done and has fixed it. https://talosintelligence.com/reputation_center/lookup?search=35.182.184.76 https://www.abuseat.org/lookup.cgi?ip=35.182.184.76
  2. petzl

    Any point in reporting spam from AMAZONAWS?

    Nearly all stopped for me also after forwarding their spam back at them with a nerdy note! That said I still get the odd multiple spam splurge at once all from different IP's Something wrong with their security. Possibly one of their home connected WiFi gadgets?
  3. You need to report to abuse[AT]amazonaws[DOT]com from Gmails WebPage Click "Show original" on your gmail WebMail page. you will see the IP that sent it to Gmail SPF: PASS with IP 52.54.105.63 Learn more Forward it to AmazonAWS paste the IP above the text you paste into forwarded message. I paste this above headers and body text Criminal phishing, bogus reply address, bogus unsubscribe (NEVER subscribed), DDoS Banned all Amazon and subsidiaries purchases because of inept AWS abuse responses to AmazonAWS DDoS multiple IP email attacks It looks to me Amazon should block port 25 to prevent viruses and spam tools managing to connect directly from infected machines through your NAT? All those who have access to your network need to scan for malware. If detected change password injection 52.54.105.63 abuseXamazonawsXcom
  4. Speak to your email provider.
  5. petzl

    Any point in reporting spam from AMAZONAWS?

    Just got a couple today from Amazon https://www.spamcop.net/sc?id=z6609487289z0285b33932067f7daed6ceaeb71b8f51z
  6. petzl

    Any point in reporting spam from AMAZONAWS?

    These are Amazon IP's so it is up to Amazon to fix or not their spam problem. I assume it is from inside Amazon Corp.
  7. petzl

    Any point in reporting spam from AMAZONAWS?

    167.89.8.98 is often in headers but probbaly spoofed Gmail tell you the IP they recieved email from Someone working for Amazon have a infected computer Everyone in Amazon simply have to run a malware scan to fix it blocking port 25 would stop it as well.
  8. petzl

    Any point in reporting spam from AMAZONAWS?

    It looks to me Amazon must block port 25 to prevent viruses and spam tools managing to connect directly from infected machines through their NAT?
  9. petzl

    reports disabled for spam [at] uce dot org

    Probably these/this forum is scrapped for email addresses.
  10. petzl

    Any point in reporting spam from AMAZONAWS?

    Same for the rest of the planet I forward abuse report to "abuse at amazon com" direct from my Gmail where it arrives Google make it easy first I put Amazon source and a sendgrid IP (may be may not be spoofed) . Gmail always put the IP that they received it on Open "See original" SPF: PASS with IP 54.240.13.49 IP from Amazon AutoACK Criminal phishing, bogus reply address, bogus unsubscribe (NEVER subscribed), DDoS Banned all Amazon and subsidiaries purchases because of inept AWS abuse responses to AmazonAWS DDoS multiple IP email attacks email server 167.89.8.98 abuseXsendgridXcom injection 52.45.146.143 abuseXamazonawsXcom THEN space click "copy to clipboard" and past it below my "preamble"
  11. petzl

    reports disabled for spam [at] uce dot org

    spam [at] uce dot org I suspect all they did was bit-bucket reports drink coffee and eat donuts? Now their new attack on spam is.... They don't have one?
  12. petzl

    reports disabled for spam [at] uce dot org

    spam [at] uce dot org no longer accepts abuse reports
  13. petzl

    reports disabled for spam [at] uce dot org

    Seems you are right, though the quote is also right. But don't get upset I often say Australians should be allowed to vote either. Just annoys me when a public service is not a service and there is nothing one can do about it, except pay taxes then die.
  14. petzl

    reports disabled for spam [at] uce dot org

    Tells me Americans should not be allowed to vote. You still get the the FTC! If voting made any difference, they wouldn't let us do it- Mark Twain
  15. petzl

    reports disabled for spam [at] uce dot org

    Hope it works, sounds like another ineffective pretend USA bludge "mates" job that needs closing! Were NEVER anygood beforehand, you think this will change?
  16. petzl

    Any point in reporting spam from AMAZONAWS?

    1st 167.89.8.98 sendgrid email server SpamCop don't pickup? 35.182.184.76 amazon botnet 2nd 167.89.8.98 sendgrid email server SpamCop don't pickup? 35.182.184.76 amazon botnet
  17. When you get Base 64 encoding (a lot of) best to just send headers only, then hit enter twice and write truncated, this saves your paid data allowance.
  18. petzl

    Any point in reporting spam from AMAZONAWS?

    Would help if you could send ONE SpamCop tracking URL https://www.spamcop.net/sc?id=z6604938278z71b6ef1a81f29722e4620c90d9fb479ez I report/foward with spam text, from email account directly to abusexamazon.com abusexsendgrid.com phishing-reportxus-cert.gov spamxuce.gov stop-spoofingxamazon.com (replace "x" with @) With this message (hasn't stopped the spam but reduced it a lot) Criminal phishing, bogus reply address, bogus unsubscribe (NEVER subscribed), DDoS Banned all Amazon and subsidiaries purchases because of inept AWS abuse responses to AmazonAWS DDoS multiple IP email attacks email server 167.89.8.98 abuseXsendgrid.com injection 44.227.253.148 abuseXamazonaws.com
  19. petzl

    No Headers

    A downgrade, I try to disable these not always successfully though? If it still works it's not broken!
  20. If you are a paid subscriber I believe it still counts/deletes your megabytes.
  21. That's the easiest, You should be able to open a *.eml file with "Notepad" or text viewer
  22. It lookas to me your email app is not seperating the headers from the body?
  23. That is working but you haven't submitted it Check with you provider that they are giving you proper headers? It may be your email APP doing this
  24. Have you tried copy and paste text headers and body manually into SpamCop parser?
  25. 212.54.57.77 is spamsource abuse[AT]as9143.net the abuse desk is asleep at wheel seems it's continually reported https://www.spamcop.net/w3m?action=checkblock&ip=212.54.57.77 Don't know why SpamCop is not picking it up?
×