应用程序引擎中接收电子邮件地址计数限制
我的邮件是关于接收电子邮件到任何地址的选项，如下所示 - [电子邮件受保护] 记录在此处：http://code.google.com /appengine/docs/python/mail/receivingmail.html
我的问题是：
对于使用上述格式创建并在应用程序内使用的电子邮件地址的数量是否有任何限制？ 我可能有一百万个用户，并且可以有某种“邮件内”设施，其中每个用户都被分配一个唯一的“xxx”id。
上述格式的地址可以接收的电子邮件数量有限制吗？我没有在任何地方看到指定的任何配额限制？
My mail is regarding the option for receiving email to any address which looks like - [email protected] documented here: http://code.google.com/appengine/docs/python/mail/receivingmail.html
My questions are:
Is there any restriction on the number of email addresses which can be created using the above format and used inside the application?
As an example I may have a million users and could have some sort of a "in-mail" facility where each user is assigned a unique "xxx" id.Is there any limit on the number of emails which can be received by an address of the above format? I don't see any quota restrictions specified anywhere?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
您可以发送或接收电子邮件的电子邮件地址数量没有限制。传入的电子邮件将简单地发送给您的处理程序，并保留地址；不会创建任何帐户，因此没有理由限制唯一地址的数量。此处仅适用对传入邮件、总请求和邮件 API 调用的系统范围配额限制。
There's no limit to the number of email addresses you can send or receive email on. Incoming email is simply sent to your handler with the address preserved; no accounts get created, so there's no reason to limit the number of unique addresses. The system-wide quota limits on incoming mail, total requests, and calls to the mail API are the only ones that apply here.
您的应用程序可以接收邮件的地址数量或它可以接收的电子邮件数量没有限制。
App Engine 不会保留您用于接收邮件的地址；每个入站消息都像 HTTP POST 一样进行处理，然后被丢弃。向一个地址发送一百万封电子邮件或向一百万个地址发送一百万封电子邮件将使用相同的资源。
与邮件相关的配额仅适用于已发送的邮件。对于 CPU、带宽等，入站邮件与 HTTP 请求来自同一资源池。文档中没有任何特定于入站邮件的配额的指示。
There is no limit on the number of addresses where your app can receive mail, or the number of emails it can receive.
App Engine does not persist the addresses you've used to receive mail; each inbound message is handled like an HTTP POST and then discarded. Sending a million emails to one address or a to million addresses will use the same resources.
The mail-related quotas apply to sent mail only. For CPU, bandwidth, etc., inbound mail draws from the same resource pool as your HTTP requests. There's no indication in the docs of any quota specific to inbound mail.
我在该格式中没有看到任何提及最多可以拥有的电子邮件地址的信息
字符串@ appid.appspotmail.com。但肯定必须指定一些内部限制。我想 appspotmail 选项并不意味着用于为每个应用程序的用户创建唯一的电子邮件（特别是如果您有大量用户）。
配额中指定了限制，例如您可以发送邮件每天最多可向 7,400,000 个收件人发送邮件，并且您每天最多可向 GAE Mail API 发出 1,700,000 次调用（这两个限制仅在启用计费时适用）。因此，如果您有一百万用户，您可能很快就会达到 API 限制，因为他们中的大多数人都会收到一封或多封电子邮件。
I can't see any mention of a maximum of email addresses you can have in the format
string@ appid.appspotmail.com. But surely there must be some internal limit specified. I guess the appspotmail option is not meant to be used to create unique emails for each of your app's users (especially if you have a large number of users).
There are limits specified in the quotas, for example you can send mails to a maximum of 7,400,000 recipients a day, and you can make a maximum of 1,700,000 calls a day to the GAE Mail API (both limits apply only when billing is enabled). So if you had a million users, you probably would reach the API limit pretty soon when most of them would receive one or multiple emails.