Amazon SES(简单电子邮件服务)用于批量电子邮件，而不是用于事务性电子邮件? [英] Amazon SES (Simple Email Service) for bulk e-mail, NOT for transactional e-mails?

问题描述

Amazon SES(简单电子邮件服务)自称为高度可扩展且经济高效的批量和事务性电子邮件发送服务".

The Amazon SES (Simple Email Service) self-described as a "highly scalable and cost-effective bulk and transactional email-sending service".

从我能收集到的所有信息，并通过仔细阅读 AWS 开发工具包以及 SES 指南和 API，它看起来非常适合交易电子邮件(即以一次性方式发送的应用程序电子邮件)，但我找不到任何关于批量发送电子邮件.

From everything that I can gather, and by perusing the AWS SDK as well as the SES guides and API, it looks great for transactional emails (i.e. application emails sent in a one-off fashion), but I cannot find anything about bulk emailing.

基于价格点，亚马逊显然希望/需要客户发送大量邮件.

Based on the price-point, Amazon clearly wants/needs customers to send very large quantities of mail.

是否期望您(作为实施 Amazon SES 的人)在每封电子邮件发送时单独拨打电话?

Is the expectation that you (as someone implementing Amazon SES) make individual calls per email send?

即如果您要向 200,000 个收件人发送营销电子邮件，您是否真的通过 curl(或其他)或使用 AWS sdk 向 SendEmail 或 SendRawEmail 发出 200K 请求?

i.e. If you are sending a marketing email to 200,000 recipients, do you really make 200K requests to the SendEmail or SendRawEmail via curl (or whatever) or using the AWS sdk?

这似乎不切实际.

推荐答案

文档现在明确指出 每条消息最多可以添加 50 个收件人.这样您就可以批量分割您的发件人列表；对于 200k 收件人，您将不得不进行 4k API 调用.批量邮件不是很方便；我猜亚马逊不会将他们的服务定位于这种特殊用途.

The docs now clearly state that you can add up to 50 recipients per message. So you can divide up your sender list in batches; for 200k recipients you would have to make 4k API calls. Not terribly convenient for bulk mails; I would guess Amazon is not orienting their service for this particular use.

这篇关于Amazon SES(简单电子邮件服务)用于批量电子邮件，而不是用于事务性电子邮件?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！