The Misconception
You're building a sales tool. You need reliable email delivery. You've heard Postmark gets 98%+ inbox placement. So you reach for their API, wire it up, and start sending cold outreach at scale.
Then your account gets suspended.
The mistake seems obvious in hindsight: Postmark doesn't permit cold prospecting. Their AUP explicitly forbids it. But the deeper issue isn't policy—it's architecture. A transactional email API and a prospecting infrastructure solve different problems, and conflating them exposes a misconception many builders share about what "deliverability" actually requires.
The Shared Reputation Trap
Postmark's inbox placement advantage comes from a specific design choice: shared, policed infrastructure. Every customer's mail rides on the same IP ranges. That's powerful—a new SaaS gets bank-grade placement for receipts on day one. But it only works because Postmark aggressively expels risky senders.
Why? Because reputation is communal. Mailbox providers trust Postmark's ranges because millions of expected, welcomed messages flow through them daily. One tolerated cold sender erodes that collective trust. From the provider's perspective, tolerating a single prospecting account degrades deliverability for thousands of transactional customers. The math is brutal: either ban cold outreach, or risk everyone's inbox placement.
So Postmark doesn't tolerate it. And they can't—the business model depends on it.
Prospecting Needs Isolated Reputations
Cold outreach can't inherit trust from shared infrastructure because its traffic is unexpected by definition. So the reputation model inverts: you build isolated identities you own and warm over weeks.
This looks like:
- Dedicated sending domains (separate from your corporate domain), authenticated with SPF, DKIM, DMARC
- Gradual ramp-up: small volumes first, engagement-positive traffic only, showing mailbox providers a consistent human-scaled sender
- Low velocity per identity: 20–50 messages per mailbox per day, scaled horizontally across multiple warmed identities
- Containment: when a campaign misfires (stale list, poor angle, complaint spike), the damage stays isolated to one warmed identity you can pause while your product emails sail on
In Postmark's model, the same campaign gone wrong gets your entire account—and every message stream in it—suspended. That's not a tuning problem; it's a structural incompatibility.
The Workflow Gap
Even if policy and reputation weren't issues, a delivery API only covers part of prospecting infrastructure.
Postmark's job ends at the mail server: message accepted, event logged, webhook fired. A cold campaign's job is to land a meeting, and the machinery between send and conversation is the actual product.
That means:
- Multi-step sequences with business-day delays, where replies, bounces, or unsubscribes halt the thread instantly (critical—roughly 50% of positive cold B2B replies land on follow-ups, not the first touch)
- Reply detection that reads your sending mailboxes, parses responses, detects autoresponders and opt-outs
- CRM handoff so live conversations land with a salesperson carrying full context
- Suppression enforcement across campaigns and lists
- Send throttling spread across mailboxes, business hours, timezones
- Analytics in the right units: replies and meetings, not deliveries
Building that atop a raw API is a real engineering project—a scheduler, state machine, mailbox polling, intent classification. Postmark never intended to cover it, and shoehorning it in violates their terms anyway.
What This Means for Builders
If you're building prospecting tooling, don't treat this as a Postmark limitation. Treat it as a signal about infrastructure architecture. Cold outreach and transactional mail are genuinely different jobs:
- Use Postmark (or SendGrid, Brevo) for product receipts, notifications, account emails—on your corporate domain
- Use a purpose-built outreach platform (or build one) for prospecting—on dedicated, warmed domains
- Never mix them. Don't prospect from your product domain. Don't send transactional mail from outreach infrastructure.
The isolation isn't a hassle—it's the whole point. One infrastructure failure doesn't cascade; reputation damage is contained; you can iterate on campaigns without risking your product's delivery. That separation, more than any feature, is what lets you scale outreach without eventually blowing up your account.
Full breakdown with sample funnel and selection parameters in the original: Postmark vs a Cold Outreach Tool: Transactional Is Not Prospecting.
Top comments (0)