knightshade Posted June 22, 2015 Share Posted June 22, 2015 I'm seeing that one of my pet spammers has adopted using a redirect via an amazonaws web page, presumably because it adds another level of obsfucation to hide/protect their target URL (https & the URL in the spam uses POST to pass a name & id string if the recipient is unwise enough to click through)... This raised a couple of questions/observations: Currently, SC reports to ec2-abuse#amazon.com[at]devnull.spamcop.net (apparently devnulls at amazon's request) & email-abuse[at]amazon.com. Looking at amazon's own reporting page at portal.aws.amazon.com/gp/aws/html-forms-controller/contactus/AWSAbuse , this references abuse[at]amazonaws.com - I'm wondering if the latter email address is equivalent to email-abuse[at]amazon.com, or ought to be used instead of/as well as? The reporting form on that same page indicates that, if used, amazon forward the complaint details to the EC2 customer (aka the spammer), which 'aint such a good idea - *sighs*... Is there a way to safely follow the redirect (in order to try to manually report the destination URL)? The usual techniques (urlquery etc) don't work as that target URL is protected by whatever scripting sits behind the amazonaws URL in the spam... Here's the SC tracking URL for any folks so inclined to have poke around: spamcop.net/sc?id=z6139877106z19ab51f56290487899361dbdef5efc87z Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.