|
Discussion Forums
|
Thread: Email Changes
 |
This thread has been recommended to become a knowledge base document
|
|
|
|
Replies:
56
-
Pages:
4
[
1
2
3
4
| Next
]
-
Last Post:
Dec 31, 2009 8:17 AM
by: dgzen
|
|
|
Posts:
371
Registered:
7/17/07
|
|
|
|
Email Changes
Posted:
Oct 21, 2009 8:25 PM PDT
|
|
|
It is our intention to make it easy to reliably send email from the EC2 environment. To help make it easier to send reliable email from EC2, we are making a few changes to our email policy.
If you are sending email from EC2, we highly suggest that you register one or more Elastic IP addresses with us by filling out this form so that we can work to keep it white-listed with anti-SPAM agencies like spamhaus.org:
http://aws.amazon.com/contact-us/ec2-email-limit-request/
Additionally, new accounts will be limited by default in the amount of email that they can send. New users wishing to send email from EC2 should apply to have this limit removed by filling out that same form. While these changes have been designed to not impact current users and running instances, please let us know if you experience any problems with your email applications. You will be contacted via email if we detect that your account is hitting the outbound email limit.
Please let us know if you have any questions,
The Amazon EC2 Team
|
|
Posts:
2,112
Registered:
7/10/08
|
|
|
|
Re: Email Changes
Posted:
Oct 22, 2009 4:30 AM PDT
in response to: ian@aws
|
|
|
Can you please detail exactly what activity is being monitored? Is it the use of standard SMTP ports?
|
|
Posts:
20
Registered:
11/10/08
|
|
|
|
Re: Email Changes
Posted:
Oct 22, 2009 4:58 AM PDT
in response to: ian@aws
|
|
|
This is great news. Will the limits be published?
|
|
Posts:
2,027
Registered:
3/15/06
|
|
|
|
Re: Email Changes
Posted:
Oct 22, 2009 5:35 AM PDT
in response to: ian@aws
|
|
|
Yes, more details please. What if we are using an SMTP relay service from EC2?
Mitch
|
|
Posts:
371
Registered:
7/17/07
|
|
|
|
Re: Email Changes
Posted:
Oct 22, 2009 10:50 AM PDT
in response to: M. Garnaat
|
|
|
We are limiting the ability to send email from an EC2 instance for new accounts only. Specifically, outbound port 25 (SMTP) to any destination address. We do not plan to publish the limits as we will be varying those as necessary to achieve the goal of making EC2 a better environment for sending email.
-Ian
|
|
Posts:
2,112
Registered:
7/10/08
|
|
|
|
Re: Email Changes
Posted:
Oct 22, 2009 11:19 AM PDT
in response to: ian@aws
|
|
|
Thanks for the clarification.
What about port 465?
|
|
Posts:
20
Registered:
3/10/08
|
|
|
|
Re: Email Changes
Posted:
Oct 22, 2009 5:23 PM PDT
in response to: ian@aws
|
|
|
Thanks for implementing those improvements! Should help restore market confidence in EC2 email solutions...
Kindly also verify that your abuse reporting interface is 100% compatible with automated email submissions from spam-traps operated by the major abuse-reporting institutions, e.g. spamhaus.org, abuseat.org, spamcop.net, mail-abuse.org, etc, so there's zero impedance-mismatch and no chance for email abuse reports to be ignored or otherwise "fall through the cracks"...
-- Richard
|
|
Posts:
371
Registered:
7/17/07
|
|
|
|
Re: Email Changes
Posted:
Oct 22, 2009 5:26 PM PDT
in response to: Shlomo Swidler
|
|
|
We aren't disclosing the exact limits on email for unverified accounts, and we will adjust our policies based on the behavior of unregistered users. For best results, our suggestion is to fill out the email request form and register one or more EIPs if you wish to send email from EC2.
-Ian
|
|
Posts:
371
Registered:
7/17/07
|
|
|
|
Re: Email Changes
Posted:
Oct 25, 2009 8:04 PM PDT
in response to: jowseyr
|
|
|
Thanks for your post. We are aware of some issues with our abuse reporting interface and are working to resolve them. We take all abuse complaints seriously and will continue to work to make it easier for abuse-reporting institutions to work with us to prevent abusive email.
-Ian
|
|
Posts:
3
Registered:
8/24/09
|
|
|
|
Re: Email Changes
Posted:
Oct 26, 2009 1:54 PM PDT
in response to: ian@aws
|
|
|
This is fantastic and should be sent out as a press release. I sent my IP information Friday, Amazon responded yesterday saying I was whitelisted, and I have sent 30+ emails in under an hour and have had no problems. Normally, I get listed as spam if I send more than 2-3 despite having correct DNS records and spf.
Huge step forward for EC2!
|
|
Posts:
7
Registered:
8/5/08
|
|
|
|
Re: Email Changes
Posted:
Oct 26, 2009 2:43 PM PDT
in response to: embarq
|
|
|
Can we get Reverse DNS setup on the Elastic IPs, this seems to be the last missing piece?
|
|
Posts:
1
Registered:
8/13/09
|
|
|
|
Re: Email Changes
Posted:
Oct 26, 2009 4:47 PM PDT
in response to: W. Andrew Loe III
|
|
|
> Can we get Reverse DNS setup on the Elastic IPs, this
> seems to be the last missing piece?
+1 on getting reverse DNS setup.
|
|
Posts:
12
Registered:
11/12/08
|
|
|
|
Re: Email Changes
Posted:
Oct 26, 2009 5:50 PM PDT
in response to: stolt45
|
|
|
> > Can we get Reverse DNS setup on the Elastic IPs, this> seems to be the last missing piece?
> +1 on getting reverse DNS setup.
As elastic IP addresses are offered, it seems only logical to allow us to set up reverse DNS on them so that we *truly* own the IP address. I'm seconding this.
|
|
Posts:
1
Registered:
6/30/09
|
|
|
|
Re: Email Changes
Posted:
Oct 26, 2009 11:29 PM PDT
in response to: joshzhao
|
|
|
I agree on the reverse DNS.
We run a high volume site (1 million users), and have had no end of problems with email after moving to EC2
|
|
Posts:
2
Registered:
10/27/09
|
|
|
|
Re: Email Changes
Posted:
Oct 27, 2009 9:29 PM PDT
in response to: mattignition
|
|
|
I too went through the process of registering my elastic IP (174.129.x.x) for sending email and now the few smtp servers I've tried sending to are no longer bouncing my emails. However, one server that I know to be using Symantec's BrightMail spam filter is marking everything from my AWS instance as spam.
I'm wondering if there might still be blacklists/databases other than the PBL from spamhaus that may contain my elastic IP address. I'm pretty sure it's not inconsistent rDNS because I've tried the same thing from another server (not AWS) and the same smtp/Brightmail server is not marking these emails as spam even though rDNS does not map back to the sending domain name.
I realize that this may be a question for Symantec but in general, it seems to me it could take a very long time to whitelist an elastic IP address that was previously blacklisted.
Any suggestions?
|
|
|
|
Sign in to the AWS Management Console
Create an AWS Account
