The circus at Amazon AWS® continues!

Amazon AWS® blocks outgoing port 25 on any new EC2® instance, and requires to use Amazon SES®. So you enable Amazon SES® and this is what they reply instantly:

Hello,
Thank you for submitting your request to increase your sending limits. We are unable to grant your request at this time because we do not have enough information about your use case.
If you can provide additional information about how you plan to use Amazon SES, we may be able to grant your request. In your response, include as much detail as you can about your email-sending processes and procedures.
For example, tell us how often you send email, how you maintain your recipient lists, and how you manage bounces, complaints, and unsubscribe requests. It is also helpful to provide examples of the email you plan to send so we can ensure that you are sending high-quality content.
You can provide this information by replying to the correspondence, in the console link below. Our team provides an initial response to your request within 24 hours. If we’re able to do so, we'll grant your request within this 24-hour period. However, if we need to obtain additional information from you, it might take longer to resolve your request.
Thank you for contacting Amazon Web Services.

In which world emailspermission needs to be granted? Isn’t email a basic internet service? Is it something so spectacular at Amazon AWS®?

The idiots that are paying for a service per hour need to be aware that Amazon AWS® is way above the clouds for emails.

Update:

It took 3 days for AWS® to activate the SES® service!

კომენტარები

ასე ცარიელია აქ ... დატოვე კომენტარი!

დატოვეთ პასუხი

თქვენი ელ.ფოსტის მისამართი არ გამოქვეყნდება.

გვერდითი ზოლი