Traffic governance
Each sending domain sends to each provider at its quota divided by the sending window, and a day that fills the bucket grows the quota, while one that doesn't is never a fault.
Traffic governance sets how fast each sending domain sends to each mailbox provider. It comes down to one rule: the quota sets the pace, and real demand sets the quota.
The quota sets the pace
Divide the quota by the sending window, and that's the pace. Take a quota of 40 to Google, the quota a domain starts with, over an 8-hour window. That's one email every 12 minutes, and mail drips out at that rate all through the window.
A bucket fills, or it doesn't
Each sending domain has a bucket for each provider. Once each day is over, every bucket is read on its own:
| At the end of the day | What happens next |
|---|---|
| The bucket filled: it carried at least 65% of its quota | Its quota grows the next day |
| It didn't fill | Its quota stays as it is, and that's never a fault |
A filled bucket shows the domain carries that traffic. That's the only thing that grows a quota.
What the quota is, and isn't
- It sets the pace, and that's all it does.
- It isn't a ceiling, a target or a debt. Nothing pushes to reach it.
- Time that isn't used is gone, and every sending window starts fresh: Natural pace, and why it isn't warm-up.
Why nothing forces a bucket to fill
Forcing a bucket to fill would fake the very evidence that growth reads. The quota would grow on demand that never existed, and the domain would pay for it with a burst.
So nothing forces it. The evidence stays honest, and quotas grow only on real demand.
Each provider has its own bucket: The four mailbox providers.