petzl

This seems posted from within Gmail to Gmail which means it is intranet spam, there is also no body in spam, Seems the headers are incomplete also. With full headers and no body, just under headers, hit enter twice and write "No body in spam" for SpamCop to work. Just mark it in Gmail as phishing

Would like some IP numbers a few track urls But if SpamCop is not working in stopping spam you need to do this yourself Just pick say five spams or more to report, All probably from same spammer This should give results on all 158 spams Learn which is the IP YOUR email server receives email from then the IP that sent it. Just report that IP by forwarding from your email The best defense is attack!

And it may bounce from there. It's in the "Marshall Islands" so don't get your hopes up? https://en.wikipedia.org/wiki/Marshall_Islands

SpamCop cannot report these spams, but it does tell you the IP address from whence they came. Also the URL in body of message With SpamCop, a "BOT", one sometimes need to step in to do spam reports more effectively. By showing you where I would of sent them, were just letting you see example

You need to forward from your email account with this preamble at top of report http://173.240.15.12 Name: lebis.disians.com IP: 173.240.15.12 Domain: disians.com\ Registrar Abuse Contact Email: mailto:abuse[AT]web.com EMAIL IP 173.240.15.12 abuse[AT]bigboxhost.com SpamCop has this wrong http://b.link/E-Leclerc-fr IP 18.208.23.249 abuse[AT]amazonaws.com Then paste headers and text body as you did for SpamCop

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

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?

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

Speak to your email provider.

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

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.

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.

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?

Probably these/this forum is scrapped for email addresses.

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"

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?

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

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.

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

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

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

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.

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

A downgrade, I try to disable these not always successfully though? If it still works it's not broken!

If you are a paid subscriber I believe it still counts/deletes your megabytes.