Send in batches.Stay inside the limit.See every envelope.
Mailroom, 01
Google enforces sending limits and anti-spam rules; smtp batches through the Gmail API on your own account.
Bulk mail that stays honest about the limit instead of promising unlimited sending.
Every send leaves from your own connected Gmail account, so the quota that applies is the one Google already sets for you.
Queued
Every address waits its turn
Recipients are dispatched in batches at a paced rate.
Nothing fires at once, so your account is not blocked.
The hopper holds the recipient list before dispatch. Addresses wait here while the batch engine decides how many go out next.
Paced
The belt moves one batch at a time
Batches are paced to respect Gmail API quotas.
You can watch progress instead of guessing.
The belt is the send queue. Each completed batch frees the next one, so the pace is set by the quota rather than by a burst.
Treads
Stamped as they pass
Each envelope receives a state stamp as it moves through the stations.
The same vocabulary you see on Campaigns and Results.
At each station an envelope picks up its mark: queued, paced, delivered or failed. That stamp follows it to the results tray.
Exploded
The parts that keep you inside the limit
Quota, pacing and consent are separate mechanisms in one console.
You can see which one is holding a send back.
The console separates into four working parts — the hopper that holds recipients, the conveyor that paces them, the gauge that watches quota, and the tray that records outcomes.
- Hopper
- Recipient list
- Conveyor
- Batch pacing
- Quota gauge
- Per-account limit
- Results tray
- Delivery record
Gauge, inside
The needle steps, it does not slide
Quota status is tracked per connected Gmail account.
You see the limit approaching before a batch is rejected.
Inside the gauge, the needle advances one tick per sent batch rather than sweeping smoothly. Ticks mark the quota threshold so you can read how close a campaign is to it.
- Tracked per
- Connected Gmail account
- Needle
- Steps per batch
- Threshold
- Gmail API quota
Consent
No stamp, no send
A campaign cannot be saved or launched without confirmed consent basis.
Compliance is a step in the machine, not a checkbox buried in settings.
The stamp press is the consent gate. Before a campaign can be saved or launched, you confirm the lawful basis for every recipient on the list. If that basis is missing, the press stays down and nothing leaves the mailroom. Consent is a physical step in the machine, not a setting you can forget.
- Required
- Consent basis confirmed
- Blocks
- Save and launch
- Applies to
- Each campaign
Four states
Queued, Paced, Delivered, Failed
The same state vocabulary is used across Campaigns and Campaign Results.
One legend to learn, everywhere in the app.
The legend plate names the four states every envelope can hold. Learn them once and they read the same on Campaigns and on Campaign Results.
Outcomes
Every envelope lands somewhere
Each recipient is recorded as delivered, failed or throttled with a reason.
You know who received the message and why the rest did not.
The tray is the record. Each recipient is filed as delivered, failed or throttled, with the reason attached, so you can see exactly who got the message.
Pacing, quota and consent — explained
- 01 · Quota
- Google sets sending limits on your Gmail account. smtp tracks usage per connected account and stops a batch before the limit rejects it.
- 02 · Batching
- Recipients are dispatched in batches at a paced rate through the Gmail API, so nothing fires at once and your account is not blocked.
- 03 · Consent
- A campaign cannot be saved or launched until you confirm the consent basis for its recipients. Read the consent explanation before your first send.
Read the pacing and consent explanation above before launching a campaign, and the batching and consent explanation when you set up your first send. Both workflows live here, in plain text, whether or not you scroll the 3D story.
- Queued
- Waiting in the hopper
- Paced
- Held to the batch rate
- Delivered
- Accepted by Gmail
- Failed
- Recorded with a reason
No comments yet. Be the first!