Your SES sending quota and send rate
On BYOS your sending speed comes from your own AWS account's SES limits. There's no rate setting in EmailFig.
On BYOS, how fast EmailFig sends is derived from your own AWS account’s SES limits. There’s no rate dial in EmailFig, and asking us to set one by hand doesn’t work: the next health check reads AWS again and overwrites it. To send faster, raise the limit in your own SES console.
The two numbers AWS gives you
Amazon SES sets two limits per account, per region:
- a maximum send rate, in messages per second
- a sending quota, the maximum number of messages in any 24-hour period
In the sandbox both are nominal, which is why EmailFig only starts pacing off the real numbers once AWS grants production access. After that AWS raises them on its own as your account builds a clean record. Your current figures are in your SES console’s account page, in us-east-1; EmailFig doesn’t display them.
How EmailFig uses them
EmailFig reads your limits when AWS takes you out of the sandbox, and on every connection health check. It then paces your sending against three bounds at once:
- Your own SES send rate, kept slightly below your ceiling to avoid throttling errors on the first burst.
- A per-account ceiling of 50 messages per second, which applies to every EmailFig account of either kind. If your AWS limit is higher, email support@emailfig.com for a manual uplift.
- Your remaining 24-hour quota, checked as the campaign runs, so a big send can’t overrun what AWS will accept today.
EmailFig shares its sending capacity fairly between BYOS accounts, in proportion to what each is allowed. BYOS and managed accounts never slow each other down.
A campaign sends at the slowest of those bounds, so a very large send takes time. That’s a feature, not a stall.
Sending faster
Ask AWS for a limit increase from your own SES console, in us-east-1. AWS decides based on your bounce and complaint rates and the reason you give. See Bounce and complaint rates AWS enforces. Once granted, EmailFig picks up the new figure on the next connection health check, within a few hours.
Sending more slowly
Lower the limit in your own SES console and EmailFig follows it on the next check. That’s the only durable way to throttle a BYOS account: a value set by hand on our side gets reverted.
If we can’t read your quota
EmailFig reads your quota before it releases each batch. If that read fails, your account is skipped for that round and picked up on the next one. Nothing is lost and no recipient is dropped. A persistent failure shows up as a health error on Settings → AWS; see AWS connection health errors.
What this isn’t
- It’s not a monthly email allowance. Your EmailFig subscription has no send limit.
- It’s not a warm-up ramp. See Warm up a new sending domain for how to pace your first sends yourself.