Outbound Wiki

Sending rate and volume controls

Managing daily volume, ramp rates and per-provider sending speeds to avoid triggering automated filters.

Set cold email limits from the mailbox outward. Give each inbox a steady operating pace, distribute growth across more mailboxes, and watch the provider response before increasing volume. The daily quota is only one control. A tighter rate limit can interrupt a sequence while the daily quota still has room. Build the plan below the provider ceiling, then raise it in small steps only when the current pace stays clean.

Prepare the sender and list

Do the sender and list check before you calculate capacity. A clean list and an isolated sending identity give the pace a chance to mean something.

A dedicated email sending domain is a single private domain used to send and receive email, with other users kept off that domain and IP.1 It gives the sender full control over domain reputation and deliverability.2 Messages can go to spam despite good practices when the sender lacks a dedicated sending domain.3

Validate each address before sending. Email validation checks whether an address is valid before an email is sent.4 Sending to invalid addresses harms domain reputation and deliverability.5 Hold the send when the list has not passed that check.

Set a mailbox limit

Set a ceiling for each mailbox before you decide total campaign capacity. Keep the pace moderate and add mailboxes when you need scale, spreading sending so no inbox builds enough negative signals to get flagged.6

Use 30 to 40 emails per mailbox per day as a working cap.7 Sending 50 to 60 emails from a mailbox is described as the fastest way to trigger Google and Microsoft spam filters. If planned volume exceeds the per mailbox cap, add sending capacity or keep the campaign volume where it is. Do not make a single inbox work faster to absorb the difference.

Segment by provider

Put the provider into the control plan before you queue messages. Separate provider queues let you change the pace for the segment that needs it without disturbing the rest.

Gmail and Outlook often respond differently, so segmenting by provider gives better control.8 Some mailbox providers also limit daily message delivery until the sender establishes a reputation.9 Give each provider its own cap, ramp schedule, and stop condition.

Add a short delay between outbound messages when provider pacing requires it. This helps prevent the sending stream from exceeding provider rate limits.10 Watch each segment on its own, and hold a segment when its response worsens.

Check hard limits before launch

Write down the limits that can stop delivery before you schedule the sequence. Keep daily recipients, cold recipients, and message speed as separate checks.

For an Outlook or Microsoft 365 account, the cold email ceiling is 1,000 recipients per day under the non relationship recipient cap.11 The 10,000 figure is a theoretical maximum for all recipients combined and includes people already in contact history.1213 A non relationship recipient is someone with whom the sender has never exchanged email.14 Every cold prospect falls into that group.15

Exchange Online has a rate limit of 30 messages per minute.16 That limit can disrupt a sending sequence even when the daily quota is still far from full.17 Set your working limit below the applicable hard limit and check both controls before release.

Ramp and monitor

Treat each increase as a release that needs a clean response before the next change. Keep the ramp slow enough that you can tell which change caused a provider response.

Increase sending volume gradually over time.18 At each step, check delivery responses, queue behavior, and rate limit errors before moving on. Set rate limits and concurrency caps so a runaway task cannot consume the entire quota.19

When the current pace runs cleanly, raise the volume in a small increment or add mailbox capacity. If errors appear, hold the ramp and inspect the pace assigned to that provider and mailbox. Rate limit errors mean the volume is too high or arriving too soon.20

What not to do

Keep these failure modes beside the sending plan. They are the shortcuts most likely to turn a provider limit into a deliverability problem.

  • Do not schedule at official sending caps simply because cold email tools allow it.21
  • Do not treat 50 to 60 emails per mailbox as normal operating volume.7 Keep the mailbox cap at 30 to 40 per day because the higher range is described as the fastest way to trigger Google and Microsoft spam filters.
  • Do not ignore rate limit errors and continue increasing volume. They indicate that sending is too high or too soon.20

Before the next send, record the mailbox cap, provider segment, hard recipient limit, message speed limit, and stop condition. Increase volume only after the current pace runs without provider errors, and add mailbox capacity when the campaign needs more room.

Tool for this

Sending from your own mailboxes, safely paced

Intedat covers the basics here properly. It sends from the Gmail, Microsoft 365 or SMTP mailbox you already own, shows SPF, DKIM and DMARC checks for a custom domain and rechecks them, and the daily limit per mailbox tops out at 100 inside a sending window you set per workflow. It will not warm a mailbox up for you, so that part stays your job.

Open Intedat

Sources

  1. 1
    “Rather than sharing an IP or domain with all other users, a dedicated email domain is a single private domain you use to send and receive emails.”
  2. 2
    “A dedicated domain gives you full control over your reputation and email deliverability.”
  3. 3
    “Not having a dedicated email sending domain often results in emails going to spam despite good practices.”
  4. 4
    “Email Validation checks whether an email address is valid before you send to it.”
  5. 5
    “Sending to invalid addresses harms your domain reputation and deliverability.”
  6. 6
    “The senders getting the best results keep the pace moderate and add more mailboxes when they want to scale, which spreads the sending so no single inbox builds up enough bad marks to get flagged.”
  7. 7
    “Cap mailbox volume at 30-40 per day; pushing 50-60 emails per mailbox is the fastest way to trigger spam filters at Google and Microsoft.”
  8. 8
    “Gmail and Outlook often respond differently, so segmenting by provider gives you much better control.”
  9. 9
    “Certain mailbox providers limit senders to thresholds (the number of messages delivered per day) until they establish a reputation.”
  10. 10
    “Front will add a short delay between each outbound message to ensure no rate limits are exceeded with your email provider.”
  11. 11
    “The actual ceiling for cold email sent from an Outlook or Microsoft 365 account is 1,000 recipients per day - the non-relationship recipient cap.”
  12. 12
    “The 10,000 figure is your theoretical max for all recipients combined.”
  13. 13
    “But that number includes people already in your contact history.”
  14. 14
    “That applies to anyone you have never exchanged email with before.”
  15. 15
    “Every cold prospect you contact falls into that bucket.”
  16. 16
    “There is also a rate limit most people never mention: 30 messages per minute.”
  17. 17
    “That one alone can wreck a sending sequence even if you are nowhere near your daily quota.”
  18. 18
    “Increase your sending volume gradually over time.”
  19. 19
    “Rate limits and concurrency caps so one runaway task can’t consume your entire quota”
  20. 20
    “Rate-limiting errors from your sending provider”
  21. 21
    “Cold email tools will happily let you schedule against those caps.”