Article

Postmark Bounce Rate Limits Explained: What Triggers a Review

By Unlimited Verifier Team ·

Flow diagram showing a Postmark send batch moving through a bounce rate check, with healthy rates continuing and high rates triggering a list cleanup.

Summary

Postmark's public guidance has referenced about 10% bounces as the level where a review becomes likely, though it is not a fixed auto-suspension switch. Because spikes can breach a short window long before the monthly average looks bad, most senders should plan around a 2% total bounce ceiling.

Postmark's public guidance has referenced a bounce rate around 10% as the review point, but most senders should plan around a 2% total bounce ceiling, since one bad batch can breach a short evaluation window long before the monthly average looks alarming.

The 10% figure is a boundary, not a target. Reaching it makes a review likely, and by then mailbox providers have already seen a large volume of undeliverable mail from your sending infrastructure. The useful planning question is how quickly you would notice a bad batch and what you would do in the next hour. This guide covers where the figures come from, which bounces count, how to calculate your rate, how to keep it low at capture and import, and how to respond if Postmark flags your account.

Quick answer

What is Postmark's bounce rate limit, and where does it come from?

Postmark does not publish a single switch that suspends every account at a fixed percentage. Its public guidance, as referenced, points to about 10% bounces as the level at which a review becomes likely. Treat that as the outer edge, and check the current wording in Postmark's documentation before relying on it.

Bounces and complaints are different signals, which is why the thresholds differ. A rising bounce rate tells a provider your list is decaying. A review point is an operational control: it marks where someone takes a closer look at the account. Reviews tend to focus on whether you caught the problem early, so the monitoring habits in this guide matter more than the number itself.

Limits are also measured over windows, not forever. A rate that looks fine across a month can still be a problem across a day.

Bottom line: Postmark's public figure is a review point around 10%. Plan to stay near 2%, and treat 10% as the edge you should never approach.

Why do transactional senders get reviewed for bounces?

Transactional mail, such as password resets, receipts and account alerts, feels low-risk because a user action triggered it. But a mistyped address at checkout produces the same hard bounce as a purchased list, and the account carries the consequences.

In typical SaaS and ecommerce setups, three patterns appear most often:

These are capture problems, so prevention is cheaper than cleanup. A hard bounce is a permanent failure. The SMTP enhanced status codes in RFC 3463 distinguish the common cases: 5.1.1 means the mailbox doesn't exist, 5.1.2 means the domain is bad, and 5.1.3 means the address syntax is invalid. Suppress each one on receipt, and block it at the form where possible.

Teams working on email verification for ecommerce and SaaS usually find that the checks belong at the point of entry, not in a periodic clean-up.

Bottom line: Transactional bounces are mostly a capture problem, which makes prevention cheaper than cleanup.

Which bounces count toward your rate?

Only some events reflect list quality, so build your bounce rate from those and handle the rest separately. Soft bounces cause the most confusion. A full mailbox may accept mail next week, so counting every temporary failure overstates the list problem.

Event Typical code Counts toward bounce rate? Correct response
Hard bounce, mailbox doesn't exist 5.1.1 Yes Suppress immediately
Bad domain 5.1.2 Yes Suppress, and fix the form that accepted it
Invalid address syntax 5.1.3 Yes Block at capture
Soft bounce, mailbox full or temporary failure 4.x.x Only once it becomes final after repeated retries Retry, then suppress after repeated failures
Policy or reputation rejection 5.7.x Usually tracked separately; check the provider's definition Fix reputation or content, not the list
Spam complaint Feedback loop report No, a separate metric Suppress, then review consent and content

Purging addresses in response to a 5.7.x rejection removes valid contacts while leaving the real problem, your sending reputation or content, untouched. Check how each provider defines its headline figure before comparing numbers across tools.

Bottom line: Only hard and final soft bounces reflect list quality. Track those as your bounce rate, and handle complaints and policy blocks as separate problems.

What bounce rate should you actually target?

Sources disagree, and the disagreement is informative. Each figure measures a different thing, on a different system, over a different window.

Source Published figure (as described in its documentation) What it measures
Amazon SES documentation Review at around 5% bounces, with pause risk near 10% Bounces on a shared sending platform; see Amazon SES bounce rate limit explained
Postmark public guidance (as referenced) Around 10% as the review point Account review; confirm the current wording
Google's email sender guidelines Spam complaints kept below 0.3% User-reported spam to Gmail
Google Postmaster Tools Monitoring of user-reported spam, where Google's guidance points to staying below 0.1% Gmail reputation for your sending domain

The gap between 5% and 10% reflects different trigger designs, not a contradiction. Both are upper bounds, and neither is a target.

Our recommendation: Use 2% total bounces as your ceiling, under 1% as the target for each stream, and 0.1% spam complaints as the complaint limit. Here is why 2%:

Bottom line: Don't plan around a provider's review threshold. Plan around 2%, so a bad batch is caught well before a review starts.

How do you calculate your bounce rate correctly?

The formula is simple: bounce rate = bounces in a window ÷ messages sent in the same window × 100. For example, 14 bounces from 1,000 sends is 1.4%. Three details change the answer:

Set up bounce webhooks so events flow back into your application. Postmark's bounce data is categorised by type, so your handler can suppress hard bounces and spam complaints in your database as they arrive. Without that, your suppression list lags behind your sends, and you keep mailing addresses that have already failed.

Bottom line: Calculate per stream and per window, not as one monthly average, or you will miss the spike that triggers a review.

How do you keep bounces low at capture, import and send time?

Prevention works in three layers: check at capture, verify before import, and monitor continuously. The right tool depends on where an address comes from.

Method What it catches What it misses Best use
Format check in the form Obvious structural errors Real-looking addresses on domains where no mailbox exists First line, no cost
Real-time API check at capture Syntax, domain, MX records, mailbox responses, disposable and role addresses Catch-all mailboxes, which can't be confirmed; engagement Signup, address change, checkout
Bulk verification before import The whole inherited list Bad data entered after the import Migrations, partner and purchased lists
Suppression from bounce webhooks Addresses that have already failed Addresses you haven't mailed yet Backstop on every stream
Periodic re-verification Decay in dormant addresses Changes between checks Quarterly for dormant segments

Each source needs a different rule:

Scenario Check Hold-back rule Why
Signup or account change Real-time single check Block Invalid; flag Risky Stops the bad address before the first send
Password reset or receipt address Check on every change Hold sends until the address is corrected A failed reset blocks account recovery
Partner, purchased or migrated list Bulk verification before first send Suppress Invalid; send Valid first Imports cause most sudden spikes
Dormant broadcast segment Bulk verification plus engagement ranking Send Risky and catch-all addresses last Decay concentrates in old data
Ongoing backstop Webhook suppression Remove on first hard bounce Catches what the checks miss

Here is a framework for a team starting from zero:

  1. Audit 90 days of bounces by source and stream. The source with the highest rate is where you start, because averages hide it.
  2. Wire bounce webhooks into your database. Suppression has to happen in minutes, not at the next manual clean-up.
  3. Gate new addresses with real-time validation through an email verification API and automation layer. Risky results are a decision for a person, not an automatic rejection.
  4. Verify every import before it reaches a stream. A single unverified batch can produce the spike in your worst window.
  5. Set per-stream alerts. Warn at 1% and stop the stream at 2%, measured over a short window. Short windows catch spikes, and stopping early protects the rest of the account.
  6. Re-verify dormant segments quarterly and keep dated results. A record of checks supports email verification compliance and hygiene and becomes evidence if a review happens. For scheduling, see email list maintenance best practices.

Bottom line: Capture checks prevent most bounces, import checks stop spikes, and per-stream alerts catch what gets through.

Hands-on tutorial: verify an import and add a capture check

Follow these steps to clean an inherited list and set up a check at signup.

  1. Export the list as CSV. Include the email column, plus signup date and source if you have them, so you can segment results later.
  2. Sign up for a free account. The Free plan covers 25 lists a month of up to 150 emails each, plus 750 deep verifications a month, but it has no API access.
  3. Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Split larger files. On Pro, each list can hold up to 25,000 emails.
  4. Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
  5. Read the three buckets. Valid addresses are safe to send. Invalid addresses should be suppressed. Risky addresses, including catch-all, disposable and role accounts such as info@, should be held back.
  6. Export results as CSV, Excel or JSON, and save the summary counts. Results are kept for 24 hours on Free and 30 days on Pro, so download them before the window closes.
  7. Automate capture. On Pro, create a key on the email verification API page. Pro includes 100,000 API emails a month. Call the single-email check from your signup handler, or send bulk batches of up to 10,000 emails per request. There are no native ESP, CRM or Zapier integrations, so this means writing the call yourself, or exporting, verifying and re-importing.
  8. Spot-check edge cases with the free email checker, for example a high-value account that came back Risky.

For catch-all domains, the catch-all email verification page explains why the mailbox can't be confirmed and how to handle those addresses.

Bottom line: Export, verify, suppress Invalid, hold Risky, and move the check into your signup flow so the list stays clean.

Worked example: one bad partner import in a 300,000-message month

The figures are illustrative. The arithmetic and plan limits are real.

Setup: A SaaS company sends 300,000 messages a month. Its baseline hard bounce rate is 0.4%, or 1,200 bounces. A partner hands over 25,000 unchecked addresses, and about 9% are invalid, or 2,250.

Without verification:

With verification:

  1. Verify the 25,000 partner addresses before sending. That fits within Pro's per-list cap of 25,000 and its 25,000 deep verifications a month, if you run deep checks on the whole batch.
  2. Suppress the roughly 2,250 Invalid addresses. That leaves 22,750 non-Invalid addresses to send.
  3. Assume a residual bounce rate of 0.5% on the verified group, or about 114 bounces (illustrative).
  4. Window: (114 + 80) ÷ (22,750 + 20,000) = 194 ÷ 42,750 = 0.45%.
  5. Monthly: (1,200 + 114) ÷ (300,000 − 2,250) = 1,314 ÷ 297,750 = 0.44%.

Holding back Risky addresses shrinks the send count further. The rate is unlikely to rise, but your own list will decide the exact figure.

Cost: One Pro month at $29. If all 25,000 deep verifications are used, that works out to $1.16 per 1,000 deep checks. Standard verification is unlimited on every plan. To compare email verification pricing across tools, divide each plan's cost by your monthly volume in thousands.

Bottom line: A batch that would have breached 2% in its window stays under 0.5% once verified, for one month's Pro subscription.

What should you do if Postmark flags your account?

Start with the notice, and limit your response to the affected stream rather than the whole account.

  1. Protect critical mail first. Verify and send to the addresses that receive password resets and receipts, such as active users and recent signups.
  2. Pause the batch that caused the spike. Don't run a re-engagement campaign while a review is open, because it will generate fresh bounces while someone is watching.
  3. Find the root cause. Identify the source with the highest bounce rate, whether that's a form, an import or an integration.
  4. Suppress and verify. Purge hard bounces, verify the rest, and keep your counts.
  5. Reply with evidence. State the cause, the number removed, the verification method and the ceiling you will stay under.

For the wider process, see the high bounce rate account suspension guide. If your sending runs through a different platform, the Mailchimp suspension, SendGrid review and Brevo suspension guides cover those processes.

Bottom line: Protect transactional mail first, pause the batch that caused the spike, and reply with counts rather than reassurance.

How long should you wait before sending at full volume?

Postmark has no published reinstatement timeline that I can point you to, so treat re-entry as a staged ramp. The sequence below is an illustrative plan, not a Postmark requirement:

If any day breaches 1%, drop back to the previous step. For the details, see how to warm up an old email list after cleaning. For dormant segments, is it safe to email a list that is two years old explains the risks. To see how one campaign affects reputation, read can a single campaign ruin sender reputation.

Bottom line: Ramp in stages, gate each step on bounce rate, and step back the moment a day breaches 1%.

What mistakes do senders make with bounce limits?

Bottom line: Most bounce problems come from averages hiding spikes and from capture points that never check addresses.

How we compared (and limitations)

This article is based on public documentation: Postmark's guidance as referenced, Amazon SES's documented thresholds, Google's sender guidelines and Postmaster Tools, and the SMTP enhanced status codes in RFC 3463. We have not tested any provider's review process. Thresholds change without notice, so check current documentation before acting on any figure here. The worked examples use illustrative bounce rates and volumes.

Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's own stated number, not an independent benchmark. If you're comparing vendors, start with the best email verification tools roundup and our guide to how to choose an email verifier. Two details matter most for transactional use: whether API access is included on your tier, and how long results are kept. For Unlimited Verifier, the Free plan has no API access and keeps results for 24 hours, while Pro includes API access and keeps results for 30 days.

Bottom line: Verify the figures in this article against current provider documentation, and choose a tool whose API access and retention fit how you send.

Worked example: catching a batch spike

Assume an illustrative import of 2,000 addresses sent in one batch.

Metric Value
Messages sent in batch 2,000
Hard bounces in batch 120
Batch bounce rate 6.0%
Monthly bounce rate (all sends) 1.1%
Plan ceiling 2.0%

The monthly figure looks healthy, but the batch is three times the 2% ceiling. Pause the stream, suppress the 120 hard-bounced addresses, and verify the rest of the import before sending again.

Frequently asked questions

What is the Postmark bounce rate limit?

Postmark's public guidance has referenced about 10% bounces as the point where a review becomes likely. It is best read as an outer boundary rather than a fixed automatic cutoff. Confirm the current wording in Postmark's documentation, since figures can change. For day-to-day planning, most senders should aim for a total bounce rate of 2% or lower.

Does Postmark suspend accounts automatically at 10% bounces?

Based on public documentation, Postmark does not publish a single rule that suspends every account at a fixed percentage. A high bounce rate makes a review likely, and the review usually looks at how quickly you detected and fixed the problem. Check the current policy wording directly before relying on any specific consequence.

Which bounces count toward the bounce rate?

Hard bounces and final soft bounces are the events that drive your bounce rate. Hard bounces indicate permanently undeliverable addresses, such as nonexistent mailboxes. Soft bounces that keep failing after retries also count. Spam complaints and policy blocks are separate signals, so they need their own fixes rather than list cleaning alone.

How do I calculate my bounce rate?

Divide the number of bounced messages in a window by the number of messages sent in that same window, then multiply by 100. For example, 120 hard bounces from 2,000 sends is a 6% rate. Calculate it per batch, per day, and per sending stream, because a monthly average can hide a short spike.

Why does my bounce rate spike after an import?

Imported lists often arrive without the suppression history from the original platform. Addresses that already hard-bounced can be mailed again, creating a burst of failures in the first sends. Verify inherited lists before they reach a live stream, and load known bad addresses into your suppression list before the first campaign goes out.

How can I keep my bounce rate low at signup?

Validate email syntax and domain format on the form, and consider a confirmation step for high-risk signups. Block or flag disposable domains, and route trial accounts with unverified addresses away from production sends. Catching typos at capture is cheaper than letting them bounce on the first transactional email.

What should I do if Postmark flags my account for bounces?

Pause the affected sending stream, identify which batch or source produced the failures, and remove hard-bounced addresses from future sends. Document what caused the problem and what you changed. Reviews tend to focus on whether you detected the issue early and responded quickly, so a clear timeline and corrective steps matter.

Should I monitor bounces per stream or per account?

Monitor both, but act on the stream level. Transactional and marketing traffic often have different list sources and risks, so a problem in one should not hide inside an account-wide average. Set alerts on short windows such as hourly or daily batches, since these catch spikes that a monthly report would miss.

Is a 1% bounce rate good enough to stay safe?

A rate near 1% across a month is generally healthy, but it does not prove safety on its own. A single bad batch can push a short window well above 5% while the monthly figure still looks low. Track rates over short windows and treat your 2% ceiling as the threshold that triggers investigation.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.