RobiBue Posted March 2, 2019 Share Posted March 2, 2019 (edited) Link removed due to giving out private information.... ? Sc admins? I was wondering if an admin, or someone with the ability to check the SC address entries can see and post here why the amazonAWS address is devnulled. When I report manually to abuse amazonaws com I get both sentient and robot replies. Can the devnull redirection be removed so that reports go again to their abuse desk? They seem to be taking care of their spammers, but only if the spam can be reported... I am not sure if abuse reports going to ipmanagement are actually going anywhere. I have seen 3 different abuse addresses listed for amazon aws and ec2, where ipmanagement seems like a fluke that ended up without an abuse address at amazon web services... Edited March 3, 2019 by RobiBue Link removed due to giving out private information.... ? Sc admins? Quote Link to comment Share on other sites More sharing options...
Lking Posted March 2, 2019 Share Posted March 2, 2019 I admit I do not know which of several reasons that amazonAWS reports are being devnulled. But in general there are several possible reasons a spam report is not sent but directed to devnull.spamcop.net The intended recipient has ask SC not the send spam reports. (SC does not want to become a "spammer" sending unwanted email) spam Reports sent to the abuse address have bounced. (a report and bounce would just clutter the bandwidth) There is evidence that the recipient is in fact the spammer not a responsible ISP. (would serve no purpose) SC did not find a valid abuse address for the IP. (Record keeping only) The Tracking URL report section does provide an explanation Quote Tracking message source: 50.112.130.188: Routing details for 50.112.130.188[refresh/show] Cached whois for 50.112.130.188 : abuse@amazonaws.com Using abuse net on abuse{AT}amazonaws.com abuse net amazonaws.com = abuse{AT}amazonaws.com Using best contacts abuse{AT}amazonaws.com Reports disabled for abuse{AT}amazonaws.com <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< Using abuse#amazonaws.com{AT}devnull.spamcop.net for statistical tracking. "<<<<<<<<<<<<<<<<<" added Quote Link to comment Share on other sites More sharing options...
Steve Posted March 17, 2019 Share Posted March 17, 2019 On 3/2/2019 at 2:11 PM, Lking said: I admit I do not know which of several reasons that amazonAWS reports are being devnulled. But in general there are several possible reasons a spam report is not sent but directed to devnull.spamcop.net The intended recipient has ask SC not the send spam reports. (SC does not want to become a "spammer" sending unwanted email) spam Reports sent to the abuse address have bounced. (a report and bounce would just clutter the bandwidth) There is evidence that the recipient is in fact the spammer not a responsible ISP. (would serve no purpose) SC did not find a valid abuse address for the IP. (Record keeping only) The Tracking URL report section does provide an explanation "<<<<<<<<<<<<<<<<<" added I just manually report those emails to abuse(at)amazonaws.com and ec2-abuse(at)amazon.com I do get replies back once they've received the spam report and when they've taken action or mitigated the activity of their subscriber/customer. Quote Link to comment Share on other sites More sharing options...
petzl Posted March 17, 2019 Share Posted March 17, 2019 13 minutes ago, Steve said: I just manually report those emails to abuse(at)amazonaws.com and ec2-abuse(at)amazon.com I do get replies back once they've received the spam report and when they've taken action or mitigated the activity of their subscriber/customer. They do act but are very bureaucratic. Try to work out where the SpamCop tracking URL is Hint it's at top of page BEFORE you submit report Quote Link to comment Share on other sites More sharing options...
Steve Posted March 17, 2019 Share Posted March 17, 2019 Has anyone gotten AmazonAWS spam originating from AAMC.org (American Association of Medical colleges) with the IP address 143.220.15.131? I've gotten several and when reporting this IP addy through SC, it parses the email and comes back with an abuse address of shammond@aamc.org. But if I perform a whois on the IP address, I get dnsadministrator@aamc.org. shammond@aamc.org does not appear anywhere in a whois query nor did I find it on the AAMC website. Here's tracking URL for one of those emails: https://www.spamcop.net/sc?id=z6530651814zff918c1118d7372ee13d0545ccf2e9d3z Reporting it through SC to shammond@aamc.org or manually to dnsadministrator@aamc.org yields no response back that they've received it and/or have taken action against this IP address to stop/mitigate spam being sent from it. Quote Tracking message source: 143.220.15.131: Routing details for 143.220.15.131[refresh/show] Cached whois for 143.220.15.131 : shammond@aamc.orgUsing last resort contacts shammond@aamc.orgMessage is 12 hours old143.220.15.131 not listed in cbl.abuseat.org143.220.15.131 not listed in dnsbl.sorbs.net143.220.15.131 not listed in accredit.habeas.com143.220.15.131 not listed in plus.bondedsender.org143.220.15.131 not listed in iadb.isipp.com clicking on Routing details for 143.220.15.131[refresh/show] reveals this info: Tracking details Display data:"whois 143.220.15.131@whois.arin.net" (Getting contact from whois.arin.net )Found AbuseEmail in whois dnsadministrator@aamc.org143.220.0.0 - 143.220.255.255:dnsadministrator@aamc.orgRouting details for 143.220.15.131Using abuse net on dnsadministrator@aamc.orgNo abuse net record for aamc.orgUsing default postmaster contacts postmaster@aamc.org If that's the case, why doesn't SC send reports to the postmaster address then? Quote Link to comment Share on other sites More sharing options...
MIG Posted March 30, 2019 Share Posted March 30, 2019 (edited) On 3/17/2019 at 4:21 PM, Steve said: Routing details for 143.220.15.131 Using abuse net on dnsadministrator@aamc.org No abuse net record for aamc.org Using default postmaster contacts postmaster@aamc.org If that's the case, why doesn't SC send reports to the postmaster address then? Hey Steve, I might be barking up the wrong blade of grass, but, have you tried logging this via: http://forum.spamcop.net/forum/39-routing-report-address-issues/ Might be worth a shot? Cheers! Edited March 30, 2019 by MIG Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.