El circo en Amazon AWS® continúa!

Amazon AWS® bloquea el puerto de salida 25 en cualquier nueva instancia EC2®, y requiere usar Amazon SES®. Habilita Amazon SES® y esto es lo que responden al instante:

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.

¿En qué mundo los correos electrónicos’ se debe otorgar permiso? ¿No es el correo electrónico un servicio básico de Internet?? ¿Es algo tan espectacular en Amazon AWS®?

Los idiotas que pagan por un servicio por hora deben saber que Amazon AWS® está muy por encima de las nubes para los correos electrónicos..

Actualizar:

Tomó 3 días para que AWS® active el servicio SES®!