Summary

  • Postmark sandbox messages can appear as delivered while going to a black hole. Processing them still counts towards monthly usage.
  • Exhausting a paid allowance does not stop sending. A shared budget for tests and customer mail needs someone authorised to choose what keeps spending.

Postmark has found a thoroughly respectable way to charge postage to a black hole. The message reaches no real inbox. The infrastructure processes it, the application can inspect it, and the monthly counter remembers it. The recipient is imaginary; the work is not.

Its sandbox-server documentation spells out the arrangement. Test messages appear as delivered in the interface, webhooks and API, although they never reach real recipients. They still pass through Postmark’s infrastructure and remain accessible through its API, so they count towards monthly sending volume.

That is a useful service. A team should be able to rehearse order confirmations, account recovery and event handling without recruiting customers as unpaid test participants. The sandbox separates the rehearsal from real inboxes. It does not automatically separate the engineering department’s wallet from the operating budget.

The allowance runs out before the service does

For paid accounts, Postmark’s pricing and billing FAQ says sending continues after the included emails are used. Additional messages attract the plan’s overage rate; disabling that additional sending or setting such limits is not possible. The free Developer plan is different: 100 emails a month with no overages. A buyer who carries the free account’s boundary into a paid budget has imported the wrong rule.

Continued sending has obvious commercial value. A customer waiting for a payment confirmation should not have to learn that an internal monthly counter just crossed a line. Postmark avoids an interruption caused by allowance exhaustion. The buyer still has to decide whether another test run deserves the same right to keep spending as the customer’s message.

The public pricing page, checked on November 1st 2026 at the 10,000-email allowance, lists Basic at $15 a month and $1.80 per additional thousand. Consider a calculation, rather than an observed customer bill: 6,000 billable production emails plus 5,000 sandbox emails make 11,000. That gives $16.80 before taxes, add-ons or plan changes. The absence of a recipient for the tests does not erase the processing.

Nobody needs a board meeting over $1.80. That is precisely why the mechanism deserves attention. The person rerunning a test is buying another quality check. The person sending customer notices is buying communication. The person receiving the invoice gets their combined decisions. A small unit price makes each instruction easy to overlook; the counter adds them with admirable discipline.

A click is an unreliable unit of account

Postmark’s monthly billing explanation counts transactional mail, broadcasts, sandbox messages and processed inbound emails. Each CC and BCC address counts separately. Inbound processing depends on the plan; Basic currently excludes it. One application action can therefore produce several billable units. Counting how often someone pressed Send is not much of a reconciliation method.

The delivery label creates a related reporting problem. A sandbox delivery event can demonstrate that a test reached a particular step. It cannot demonstrate arrival in a customer’s inbox. Mix it into customer-contact statistics and the business may appear busier than it was. Remove it from the explanation of costs and real processing disappears. The vendor documents the boundary. The buyer has to preserve it in its own reports.

Different tests buy different evidence. The official testing guide offers a public API test token that validates calls and returns a response. It does not produce activity history, actual sending or simulated bounces. Checking a request has a legitimate place; it cannot stand in for every exercise of an integration. Replacing deeper tests with it would first reduce the behaviour being checked, whatever happened to the budget.

Billing time makes responsibility easier to postpone. The base subscription is paid in advance. Overage from the previous cycle appears on the next invoice, and unused allowance does not roll over. The notification that the included emails have been consumed is a warning bell; paid sending continues. If the first serious conversation about repeated tests begins when finance opens the invoice, prior authorisation has become a retrospective memory contest.

The terms for new customers name AC PM, LLC as the contracting party. There is a name on the supplier’s side of the paperwork. There should be one inside the buyer’s organisation too: someone able to distinguish a repeatable test, a deferrable batch and a message with a customer deadline.

The black hole is an excellent substitute recipient. Promoting it to budget manager would be a mistake.