MailcrateSending Quotas
Your workspace's sending limits, the bounce and complaint safeguards, and what happens when sending pauses.
Mailcrate applies a few limits to every workspace. They exist to keep your sender reputation, and that of everyone on the platform, in good shape. Settings → Workspace → Usage & Limits shows where you stand on each.
Daily and monthly limits
Each workspace has a daily and a monthly sending allowance. The Usage & Limits page shows how much of each is left.
- Every email Mailcrate sends counts: campaigns, journeys, transactional messages and API sends alike. Sends blocked by the suppression list or an unsubscribe don't.
- Daily usage resets at midnight UTC. Monthly usage resets on the 1st, also in UTC.
- A campaign's Delivery step shows how much of today's quota it would use before you send.
When a limit is reached
- A new campaign can't be sent. The send dialog says which limit was hit and when it resets.
- API and transactional sends are refused, with the time to retry after.
- Email already on its way out, such as the rest of a large campaign or a journey's next email, isn't dropped. It waits and goes out once the limit resets. Anything still held after seven days is given up and shows as Rejected in the delivery log.
If you need higher limits, contact Mailcrate support.
Bounce and complaint safeguards
Mailcrate checks your bounce and complaint rates every few minutes, over the email you sent in the last seven days. Usage & Limits shows both rates next to their thresholds, under Deliverability protection.
The rates only count once you have sent at least 250 emails in those seven days; until then they show as Not evaluated and can't pause sending. A handful of bounces from a small test send won't trip anything.
| Rate | Pauses sending above |
|---|---|
| Bounce rate | 5% |
| Complaint rate | 0.1% |
The bounce rate includes both hard and soft bounces. The complaint rate counts recipients who marked your email as spam.
These match the thresholds mail providers use to judge senders. Crossing one usually means a list with old or invalid addresses, or people receiving email they didn't expect.
When sending is paused
If a safeguard trips, or the Mailcrate team pauses a workspace while reviewing its activity, a banner across the app says Sending is paused and why. When a safeguard trips, the workspace's owners also get an email about it. Your account, data and drafts are unaffected; only sending stops:
- New campaigns can't be sent, and API and transactional sends are refused.
- Email that was already queued waits rather than being dropped, and goes out once sending resumes, as long as that is within seven days.
You can't resume sending yourself. The Mailcrate team reviews the activity, contacts you, and lifts the pause once the cause is dealt with.
While you wait, look at what caused it: check the delivery log for the bounced or complained messages, and where those addresses came from.
If your workspace is provisioned by another organization (for example a platform that creates Mailcrate workspaces for its customers), that organization can also suspend sending. Then only they can resume it.
Other rules on the same page
- Frequency cap limits how many marketing emails one contact can receive in a rolling window, across campaigns, journeys and API sends. Set it as Emails per contact (1 to 50) within a Window in hours (1 to 720, so up to 30 days). When a contact is at the cap, a campaign skips them and counts them on its report, a journey waits until the window has room again, and an API send is recorded as suppressed. Transactional email is never counted or capped. Only owners and admins can change it.
- Sending window sets the days and hours new campaigns may send in by default. Each campaign can change it; see Scheduling.
A new workspace's first campaign to more than 1,000 recipients is also held for a one-time review; see Review & Approval.