�️ DeepSyte

Sender Warmup and Daily Limits

Understand warmup mode, manual mode, domain caps, inbox caps, and the campaign capacity calculation.

Every campaign send is checked against the lowest active limit. A user can choose guided warmup or manual limits for prewarmed senders.

Limit modes

ModeBehavior
warmupDeepSyte calculates a safe cap from sender age and caps it at the configured inbox/domain limit.
manualThe user sets the daily limit for a prewarmed sender. DeepSyte warns but does not block.

Warmup is the default for new sender domains.

Warmup defaults per inbox

Sender ageCap
Days 0-75/day
Days 8-1410/day
Days 15-2115/day
Days 22-3020/day
Days 31-4525/day
Days 46-6030/day
Days 61-9035/day
90+ days40/day hard max

Effective sending capacity

Campaign sending uses the lowest active limit:

  • Inbox daily limit.
  • Domain daily limit.
  • Campaign daily limit.
  • Warmup or manual mode cap.
  • Send window.
  • Weekday-only rule.
  • A hard 5 minute gap between campaign emails for the account owner.
  • Per-inbox pacing with a daily first-send offset and deterministic spacing jitter.
  • Suppression status.
  • Report quality gate.

If any gate blocks a row, cron defers it instead of bypassing limits.

Pacing

Campaign emails are sent one at a time. DeepSyte waits at least 5 minutes between campaign emails for the same account owner, then also checks the selected inbox's own pacing. Each inbox gets a stable daily first-send offset and spacing jitter based on its send window and effective daily cap, so warmup inboxes do not all send at the same minute.

For example, a new warmup inbox at 5/day inside a 9am-4pm window is paced across the day instead of sending five messages back-to-back. If cron finds a row too early, it leaves the row pending and tries again later.

Auto-pause

DeepSyte pauses senders when AgentMail returns auth failure, provider rate limit, repeated send errors, or suspicious provider responses. The Inbox page shows the pause reason.

On this page