Email

Monitor Postmark with MrCron

MrCron mirrors Postmark sent, bounced, and spam-complaint counts every 5 minutes so you can see transactional email health next to signups, checkouts, and other business events.

How MrCron monitors Postmark

  • Sent and bounced counts for the last 24 hours per server.
  • Bounce rate calculated over the last 24 hours.
  • Spam-complaint count for the last 24 hours.
  • Auth-failure detection with an amber Rotate key CTA when the server token stops working.
  • Alert rules that fire on bounce-rate spikes via any notification channel.

What you will see

Sent, bounced, bounce rate, spam complaints (24h) on your project card.

Auth flow: API Key. Credentials are stored encrypted at rest with AES-256-GCM and never returned to your browser.

Start monitoring Postmark

Sign in, create a project, and connect Postmark in under a minute. First check ships in the free tier.

Start monitoring Postmark

Frequently asked questions

What Postmark credentials does MrCron need?
A Postmark server API token with read access. MrCron stores it encrypted at rest and only decrypts it inside the sync worker.
Does MrCron support multiple Postmark servers?
Yes. Attach one Postmark integration per project; each carries its own server token.
How is bounce rate calculated?
MrCron pulls the Postmark bounces endpoint counts for the last 24 hours and divides by total sent, matching what you see in the Postmark UI.
Can I alert on a rising spam-complaint count?
Yes. Create an alert rule on the postmark_spam_complaints_24h metric with a threshold above your baseline and route it to any channel.
Want the full concept-level detail? See MrCron docs for how projects, checks, and sync cadence work.