Skip to main content
Mailbox providers (Gmail, Outlook, Yahoo) decide inbox vs spam mostly by domain reputation: who you send to, how recipients react, and how fast volume grows on a new domain. This page explains what Gork enforces, what is your job, and the exact numbers involved.

​
What Gork enforces (pattern brakes, not calendars)

Paid workspaces get their full quota from day 0 — there is no warmup period, no ramp, no locked volume. Instead, sending pauses only when traffic looks abusive or reputation collapses: Legitimate conversational agent mail — low volume, real replies, high engagement — never trips any of these.

​
Your job: ramp new domains gradually

A brand-new custom domain has no reputation. Day-one blasts to thousands of cold addresses will spike bounces and complaints and trip the breaker above — on any provider, not just Gork. Ramp instead:
1

Start small and engaged

Begin with 25–100 sends/day to recipients most likely to engage (existing users, warm contacts). Engagement is a positive reputation signal.
2

Grow ~1.5–2x daily while healthy

Double-check bounce and complaint rates each morning (per-domain numbers live on the Domains page). If both are near zero, grow; if climbing, hold volume and clean the list.
3

Clean before you scale

Run lists through an email-verification tool first. Invalid addresses are the fastest way to spike bounces past 5%.
4

Skip tracking pixels during ramp

Open tracking adds a pixel some providers flag as marketing-like. Gork’s trackOpens defaults to off — leave it off until the domain is established.

​
Ramping over the API

There is no campaign scheduler — pace the loop yourself. Send idempotently so retries never double-send:

​
Voluntary domain ceilings

On the Domains page you can set a daily sending ceiling per verified domain — a static cap you control that never changes on its own:
  • NULL (default) means no ceiling; plan and workspace caps still apply.
  • Sends past the ceiling fail with 429 domain_daily_cap_reached, including the exact usage (used, cap) and the UTC-midnight resetsAt — plus a Retry-After header. Nothing is silently dropped or queued.
  • Failed provider attempts refund the day’s count, so used always equals mail actually accepted.
  • Setting a ceiling below today’s already-sent count pauses the domain until reset — the console warns you before saving.
Use it as your own guardrail: set day one’s budget, raise it as the domain proves itself, remove it when established. Programmatic control lives at PATCH /v1/domains/{id} — see Update domain ceiling.

​
Monitor, don’t guess

  • Per-domain health (Domains page, or GET /v1/domains/{id}/health): today’s ceiling usage with exact reset time, plus 7-day bounce/complaint rates against the suspension thresholds, with plain-language guidance.
  • Suppressions (GET /v1/suppressions): every bounce, complaint, and unsubscribe on record — your cleaning list.
  • Webhook deliveries (GET /v1/webhooks/deliveries): confirm email.bounced / email.complained events reach your systems in real time.
Transactional mail (password resets, receipts, OTPs) should never be throttled by warmup logic — it is expected, engaged traffic. Ramp only bulk/outreach volume.