|
Discussion Forums
|
Thread: EC2 Instance IP Black Listed at spamhaus.org
|
|
|
Replies:
75
-
Pages:
6
[
1
2
3
4
5
| Next
]
-
Last Post:
Dec 23, 2009 2:26 AM
by: alexeyfmm
|
|
|
Posts:
15
Registered:
3/27/09
|
|
|
|
EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 6:00 AM PDT
|
|
|
Hi
We have an instance with IP address "75.101.234.193". All the emails that are generated from this instance are getting blocked by the recipient email server due to the IP being listed in spamhaus.org. Please check below link
http://www.spamhaus.org/sbl/sbl.lasso?query=SBL79954
Looks like the whole IP block is black listed due to some spammer attack. Please take action and clear our IP as soon as possible.
Thanks
Asif Mushtaq
|
|
Posts:
5,320
Registered:
3/19/07
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 6:15 AM PDT
in response to: etilize
|
|
|
Amazon does not get involved in this. You can try attaching an Elastic IP to the instance and ask spamhaus to whitelist that ip address.
|
|
Posts:
15
Registered:
3/27/09
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 6:57 AM PDT
in response to: Allen
|
|
|
Thanks for the comment Allen. Did you check the link that i have posted it says that the whole /17 block is listed and only amazon.com can get it cleared. Please let me know if i am missing something.
Asif
|
|
Posts:
5,320
Registered:
3/19/07
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 7:27 AM PDT
in response to: etilize
|
|
|
As I said, Amazon does not get involved in this. You will have to come up with a workaround. See my prior post for one possibility.
|
|
Posts:
1,265
Registered:
10/10/07
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 7:30 AM PDT
in response to: Allen
|
|
|
Another possibility is using a third-party SMTP service. Search the forums for 'authsmtp' for more information.
|
|
Posts:
20
Registered:
11/10/08
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 8:22 AM PDT
in response to: etilize
|
|
|
My service that runs in EC2 is having all email from my reserved IP blocked due to this Spamhaus issue. Spamhaus claims they cannot whitelist individual IPs from this rule. As hard as I find that to believe, it's what they are saying.
They are waiting to be contacted by Amazon.
To quote the email sent to me:
Unfortunately we have no way to do that without removing this listing entirely. Our system doesn't let us "punch holes", and networks are not friendly to that kind of thing. What we need is for Amazon to control this spammer, who is abusing the clouds both at Amazon and at Rackspace/Slicehost and has been for six to eight weeks now. The spammer is not simply sending spam; he or she has also sent phishes and malware, which can do real damage to naive or inexperienced users.
As soon as Amazon contacts us, there are a number of measures we could take with their help to corral this spammer and limit their effect on others. But we can't do most of these things by ourselves; we can only block the spammer as we are doing. :(
So please contact Amazon and ask them to contact us.
So, somebody from Amazon, please give Spamhaus a call about this.
"Amazon does not get involved... you'll have to find a work-around" - that's unacceptable. This is affecting ALL EC2 customers sending mail. Get off your high horse and work with Spamhaus on this.
|
|
Posts:
114
Registered:
3/28/06
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 9:10 AM PDT
in response to: Matt W
|
|
|
This is an ongoing problem that isn't going to go away... even if you get it fixed Spamhaus will block the IP range again the next time somebody hosts a spam server here...
It seems like the "right" answer for Amazon from a customer service perspective would be to provide a trusted SMTP relay for EC2 instances that is actively policed to block spammers.
Make it a new AWS service, and charge us all $0.001 a message. I would sign up in a second, and the pricing would deter the spammers.
(Obviously, Amazon has some fairly significant SMTP infrastructure to send their own email... just rent some of it to us...)
|
|
Posts:
8
Registered:
7/13/09
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 9:11 AM PDT
in response to: Allen
|
|
|
Allen,
Spamhous, as Matt already told sent us the same statement - they tell they cannot whitelist 1 IP address when entire IP range is blocked.
Our instance with IP: 75.101.128.97 and we are also affected and can do nothing?
According to your terms of use for EC2, spamming is forbidden, you know exactly who is doing that and you can stop them from spamming and at least answer to spamhaus about their request.
Please advise.
Alexei
|
|
Posts:
5,320
Registered:
3/19/07
|
|
|
Posts:
1,265
Registered:
10/10/07
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 9:50 AM PDT
in response to: lekruscmw
|
|
|
Alexei,
It seems you are confused about one point: Allen does not work for Amazon. Amazon employees have @AWS at the end of their moniker and have the AWS symbol beside their posts.
|
|
Posts:
371
Registered:
7/17/07
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 11:02 AM PDT
in response to: etilize
|
|
|
We are currently reaching out to SpamHaus to understand what steps need to be taken to remove our IP-address range from their RBL. We are treating this with high priority.
Regards,
-Ian
|
|
Posts:
20
Registered:
3/10/08
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 12:00 PM PDT
in response to: etilize
|
|
|
We (death2spam.net) operate a high-precision anti-spam SMTP interception cluster in EC2, using 3 elastic IP addresses which had all been "cleared" at Spamhaus (a year ago) for relaying scrubbed emails to customer's mail servers. Not any longer. Yesterday, to our customer's complete dismay, many emails suddenly began to get hard-failed (rejected) by their mail server, since they appear to originate from a spam zombie or blocked relay.
We assumed (stupidly) that Amazon's zero-tolerance policy for spammers provided us some kind of immunity from such blocking. We were given no warning of this massive disruption to our SMTP transmissions, thus couldn't warn clients to white-list our server IP addresses from DNSBL lookups.
We insist that any spammer operating in EC2 be aggressively closed down, since this RBL listing causes a massive interruption to our core business, and has the potential to undo years of hard work gaining customer's trust in the reliability of our email delivery infrastructure -- ironically, the very reason we migrated onto EC2.
Come on, Amazon, get this idiocy sorted out FAST, and make sure it doesn't ever happen again!
|
|
Posts:
8
Registered:
7/13/09
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 12:22 PM PDT
in response to: Colin Rhodes
|
|
|
Colin, thanks for your note.
Allen, sorry, I thought you are from Amazon.
Ian, thank you for your answer and attention to this issue, hope that will be resolved soon.
|
|
Posts:
13
Registered:
10/14/09
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 2:51 PM PDT
in response to: jowseyr
|
|
|
jowseyr,
Having been the victim of these spam-fighting organizations several times in the past, we can say this is more than frustrating. At the same time, having been the direct subject of spam reports going into Amazon, I can say two things:
1) Amazon really does respond proactively
2) Some spam-fighting organizations are less then honest
Let me explain (2). I do not believe they are being dishonest on purpose, but the reporting tools they use flawed. As an example, we operate a number of mailing lists which run on Amazon's servers, some of those mailing lists are used to carry out functions of the United Nations.
As with all mailing lists, users sometimes change their email addresses and do not report those to us. Over time, previously-assigned addresses become spam trap addresses. In other cases, our server receives messages that have forged headers. Though we employ SPF to block that and will employ DKIM's policy enforcement as soon as the industry is ready, most domains do not set policy records. As a result, forged mail gets through, which is then politely rejected by our mailing list software.
Unfortunately, both classes of email have resulted in our server getting flagged for attempting to send spam when, in fact, in every single instance, it has merely been our mail server attempting to deliver mail exactly as it is supposed to do. Spam reporting companies never examine the contents of messages to see that they are or are not spam, just declaring us guilty immediately and adding us to their blacklists. UCE PROTECT has been the worst-- a completely useless and uncooperative organization. The others have generally been cooperative, but have not implemented proper procedures and refuse to grant our IP addresses exception.
Personally, I applaud Amazon's efforts. A change in approach on the part of the blacklist organizations is very much needed.
|
|
Posts:
20
Registered:
3/10/08
|
|
|
|
Re: EC2 Instance IP Black Listed at spamhaus.org
Posted:
Oct 14, 2009 3:08 PM PDT
in response to: ian@aws
|
|
|
High-priority means it gets fixed FAST. This issue is now losing us customers! EC2 is about to get slammed in the trade press, I can assure you...
WARNING to anyone intending to operate a commercial-grade high-availability email system in EC2: don't do it! The risk to your core business of EVER getting blocked by an RBL or DNSBL is a fatal show-stopper. If Amazon cannot guarantee that their network IP space won't be black-listed for email delivery, it's not worth migrating into EC2, only to find you've got to move again. A very time-consuming and expensive undertaking!
Amazon is about to lose $1000 worth of our business per month. What, we need to spend $400 now on Gold Support, just so we can get told it's a "high priority"? No, guys, it's an EXTREMELY URGENT MESS of the worst kind. We currently have hundreds of very angry customers demanding a time-of-resolution, and we're utterly powerless to convince SpamHaus to unblock our IP addresses, or do anything to hurry Amazon along...
Please, please, please, you gotta get this FIXED!
|
|
|
|
Sign in to the AWS Management Console
Create an AWS Account
