Jump to content

petzl

Memberp
  • Content Count

    2,487
  • Joined

  • Last visited

Everything posted by petzl

  1. petzl

    Why organisation ip Blacklsited?

    SpamCop blocklist can be activated by a large number of emails hitting "SpamCop's spamtraps" . These email addresses are not public but can be scraped by "bots" from poisoned Web-sites. Records of such attacks are not recorded will be blocked for 24 hours from last spam. Two reasons for this is someone is not using a Virus scanner and a computer/device has been compromised or best practice for marketing is not being done "double opt-in confirmation" Minimum is https://en.wikipedia.org/wiki/Opt-in_email#Best_practice How easy is it to be put on a/your mail list? Your competitors may well try to sabotage your mail list by loading it with poisoned email addresses?
  2. petzl

    Why organisation ip Blacklsited?

    No reports made by SpamCop members for 90 days which is as long as records are kept? Can you show the bounce, edit it to remove any sensitive information
  3. petzl

    Any point in reporting spam from AMAZONAWS?

    I just forward to "abuse [AT] amazon [DOT] com" "stop-spoofing [AT] amazon [DOT] com" From my Gmail account directly
  4. petzl

    Any point in reporting spam from AMAZONAWS?

    Sometimes SpamCop reports re ignored! These creeps I report directly from the email account they attack
  5. petzl

    Any point in reporting spam from AMAZONAWS?

    I always forward my Amazon spam to abuse [AT] amazon [DOT] com which now has stopped from amazon spammer has moved to India https://www.spamcop.net/sc?id=z6614613333z33924b4aa692bdb379203b970853f7efz Creep is using a number of Indian IP's but same fingerprint as Amazon spam "contact[AT]gyaneshwarcomputer[DOT]com" "abuse[AT]alphainfonet[DOT]com" "admin[AT]mukeshtech[DOT]com"
  6. That's all I do with mine Seems though when spammer sends though gmail to gmail becomes a intranet SpamCop cannot parse Just report as phishing and gmail will deal with it Reported a while ago https://www.spamcop.net/sc?id=z6613089010zeca3f141148e65c17956cc77885b5331z
  7. Working for me two days ago? Fake drug spam. https://www.spamcop.net/sc?id=z6612624629z1abe5cddebae09ba94ce8ea7968ce25bz
  8. 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
  9. petzl

    Spams received already outdated

    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!
  10. petzl

    Spams received already outdated

    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
  11. petzl

    Spams received already outdated

    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
  12. petzl

    Spams received already outdated

    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
  13. 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
  14. 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?
  15. 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
  16. Speak to your email provider.
  17. petzl

    Any point in reporting spam from AMAZONAWS?

    Just got a couple today from Amazon https://www.spamcop.net/sc?id=z6609487289z0285b33932067f7daed6ceaeb71b8f51z
  18. 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.
  19. 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.
  20. 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?
  21. petzl

    reports disabled for spam [at] uce dot org

    Probably these/this forum is scrapped for email addresses.
  22. 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"
  23. 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?
  24. petzl

    reports disabled for spam [at] uce dot org

    spam [at] uce dot org no longer accepts abuse reports
  25. 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.
×