All help articles

Sending limits for plans and users

Every user has three sending limits, plus a storage quota and a largest message size. Each plan sets them for everyone on it, and the SaaS administrator can give one user their own values instead.

What is counted

• Recipients per hour and recipients per 24 hours: every recipient of every message counts, so one message to 10 people uses 10. Both are rolling windows: a message sent at 14:05 stops counting toward the hour at 15:05.
• Recipients per message: recipients past this number are refused, and the rest of the message goes through.

All of these count, from the same allowance:

• mail sent from a mail app over the submission port,
• mail sent from webmail,
• vacation replies,
• filter redirects to other domains.

Mail between users on Zappocity counts too: the limit is on sending, not only on mail leaving the platform.

When a user reaches a limit, a mail app gets "sending limit reached, try again later" and webmail shows the same message above the Send button, with the message kept in Drafts.

Setting limits for a plan

In the admin panel, open Plans, choose Edit on a plan, and change Recipients per hour, per user, Recipients per 24 hours, per user or Recipients per message. The plans list shows each plan's sending limits. A change applies to every user on the plan from their next message. 0 per hour or per day stops everyone on the plan sending.

API: PATCH /v1/plans/{plan} with {"limits": {"sendPerHour": 200, "sendPerDay": 1000, "maxRecipients": 100}}.

Giving one user their own limits

Use this to raise the limits of a trusted user who sends a lot (a newsletter sender, a sales team member), or to hold back one who is misbehaving without suspending them.

1. In the admin panel, open Tenants and the user's tenant.
2. In Users, choose Limits on the user's row.
3. The panel shows how much the user has sent in the last hour and 24 hours and how much mail they store, against the limits in effect.
4. Type a value in any field to replace the plan's for this user. Empty fields show the plan's value and keep using it.
5. Choose Save limits. They apply from the user's next message.

A user's own value can be higher or lower than the plan's. To put a user back on the plan's limits, empty the fields and save.

The fields are: mail storage, largest message, recipients per hour, recipients per 24 hours and recipients per message. A largest message above the server's own limit (CORPSUITE_MAX_MESSAGE_BYTES, 50 MB by default) has no effect.

API:

• GET /v1/tenants/{tenantId}/accounts/{accountId}/limits returns the plan's limits, the user's own (null where the plan's applies), the limits in effect and the usage.
• PUT /v1/tenants/{tenantId}/accounts/{accountId}/limits replaces the user's own limits, for example {"sendPerHour": 50}. Fields left out go back to the plan's value; {} clears them all.

Not there yet

• Limits for a whole tenant or domain in place of the plan's.
• Domain administrators setting their own users' limits; only the SaaS administrator can for now, until the domain admin panel arrives.
• Attachment size, mailing lists and API rate limits.