--- name: pp-postmark description: "One account token for every Postmark server, and a local archive that outlasts Postmark's 45-day retention. Trigger phrases: `did my email get delivered`, `check postmark bounces`, `why didn't they get the reset email`, `push postmark templates`, `postmark sending stats this week`, `set up postmark for a new project`, `use postmark`, `run postmark`." author: "Cathryn Lavery" license: "Apache-2.0" argument-hint: " [args] | install cli|mcp" allowed-tools: "Read Bash" metadata: openclaw: requires: bins: - postmark-pp-cli install: - kind: go bins: [postmark-pp-cli] module: github.com/mvanhorn/printing-press-library/library/productivity/postmark/cmd/postmark-pp-cli --- # Postmark — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `postmark-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows: ```bash npx -y @mvanhorn/printing-press-library install postmark --cli-only ``` 2. Verify: `postmark-pp-cli --version` 3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill. If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into `$GOPATH/bin` (default `$HOME/go/bin`), so add that directory to `$PATH` instead: ```bash go install github.com/mvanhorn/printing-press-library/library/productivity/postmark/cmd/postmark-pp-cli@latest ``` If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. Postmark gives every server its own token and keeps message history for 45 days by default. This CLI takes one account token and works across all your servers. Pick a server by name with `--server`, sync messages and bounces into a local SQLite archive that keeps what Postmark expires, and ask questions that span the account, like which server stopped sending or why one customer never got a password reset. It covers all 87 documented API operations, including message streams, webhooks, suppressions, and bulk email, which Postmark's official specs leave out. Sending is safe to hand to an agent. Send commands print a preview until you add `--send`, `--sandbox` validates a message with Postmark's test token without delivering it, and `email send-once` won't send the same message twice when a script retries. ## When to Use This CLI Use this CLI to operate Postmark from a terminal or an agent: check whether a specific recipient got an email, triage bounces and suppressions, move templates between servers and gate them in CI, send transactional mail safely, and watch sending health across every server in one account. The local archive answers questions about messages older than Postmark's retention window. ## Anti-triggers Do not use this CLI for: - Do not use it for Postmark billing, team members, or account settings that only exist in the web dashboard. - Do not use it for DMARC digest reports; those come from Postmark's separate DMARC API with its own token. - Do not use it to receive inbound email in real time; configure an inbound webhook instead. - Do not use it for newsletter list management; Postmark sends broadcasts but does not manage subscriber lists. ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### Account-wide oversight - **`pulse`** — Compares each server, stream, or tag with its own recent weeks and flags any that stopped sending, dropped off, or spiked in bounces or spam, across every server on the account token. _A mailer that breaks quietly stops sending instead of throwing errors, so run this weekly to catch the drop._ ```bash postmark-pp-cli pulse --window 7d --baseline 28d --agent ``` - **`recipient-domains`** — Groups sends, bounces by type, complaints, suppressions, and opens by the recipient's mailbox domain across every synced server, so one provider's problem stands out. Run sync first. _Start here when several missing-email reports come from the same provider or company._ ```bash postmark-pp-cli recipient-domains --window 7d --min-sent 20 --agent ``` - **`servers bootstrap`** — Creates a new project's Postmark server with its message streams, webhooks, sending-domain DNS records, and templates copied from another server. Prints the plan until you add --apply. _Hand this to an agent setting up email for a new project. Reruns never create a duplicate server._ ```bash postmark-pp-cli servers bootstrap "Lumen" --broadcast-stream --agent ``` ### Safe sending - **`email send-once`** — Sends an email at most once per key within a window (15 minutes by default), so an agent or script that retries after an error cannot deliver a second copy. Previews until you add --send. _Built for one-time codes, receipts, and follow-ups that an agent might retry._ ```bash postmark-pp-cli email send-once --key otp-4821 --from "$SENDER" --to "$RECIPIENT" --subject "Your code" --text "Code: 4821" --agent ``` ### Templates as code - **`templates check`** — Validates every template and layout on a server or in a pulled folder, and exits non-zero on render errors, missing test-model keys, or broken layout links. _Run it in CI before pushing template changes to a server._ ```bash postmark-pp-cli templates check --agent ``` ## Command Reference **bounces** — Manage bounces - `postmark-pp-cli bounces activate` — Activate a bounce - `postmark-pp-cli bounces delivery-stats` — Get delivery stats - `postmark-pp-cli bounces dump` — Get bounce dump - `postmark-pp-cli bounces get` — Get a single bounce - `postmark-pp-cli bounces list` — Get bounces **clicks** — Manage clicks - `postmark-pp-cli clicks get` — Retrieve Message Clicks - `postmark-pp-cli clicks list` — Clicks for a all messages **data_removals** — Manage data removals - `postmark-pp-cli data-removals create` — Request irreversible removal of a recipient's data (enabled on request by Postmark) - `postmark-pp-cli data-removals get` — Check a data removal request **domains** — Manage domains - `postmark-pp-cli domains create` — Create a Domain - `postmark-pp-cli domains delete` — Delete a Domain - `postmark-pp-cli domains get` — Get a Domain - `postmark-pp-cli domains list` — List Domains - `postmark-pp-cli domains rotate-dkim` — Creates a new DKIM key to replace your current key. - `postmark-pp-cli domains update` — Update a Domain - `postmark-pp-cli domains verify-dkim` — Request DNS Verification for DKIM - `postmark-pp-cli domains verify-return-path` — Request DNS Verification for Return-Path - `postmark-pp-cli domains verify-spf` — Request DNS Verification for SPF (deprecated by Postmark) **email** — Manage email - `postmark-pp-cli email bulk-list` — List bulk requests on this server, newest first - `postmark-pp-cli email bulk-status` — Get the status of one bulk request - `postmark-pp-cli email send` — Send a single email - `postmark-pp-cli email send-batch` — Send a batch of emails - `postmark-pp-cli email send-batch-with-templates` — Send a batch of email using templates. - `postmark-pp-cli email send-bulk` — Send one message to many recipients (bulk). Requires account approval. - `postmark-pp-cli email send-with-template` — Send an email using a Template **inbound** — Manage inbound - `postmark-pp-cli inbound bypass` — Bypass rules for a blocked inbound message - `postmark-pp-cli inbound get` — Inbound message details - `postmark-pp-cli inbound list` — Inbound message search - `postmark-pp-cli inbound retry` — Retry a failed inbound message for processing **inbound_rules** — Manage inbound rules - `postmark-pp-cli inbound-rules create` — Create an inbound rule trigger - `postmark-pp-cli inbound-rules delete` — Delete a single trigger - `postmark-pp-cli inbound-rules list` — List inbound rule triggers **messages** — Manage messages - `postmark-pp-cli messages dump` — Outbound message dump - `postmark-pp-cli messages get` — Outbound message details - `postmark-pp-cli messages list` — Outbound message search **opens** — Manage opens - `postmark-pp-cli opens get` — Retrieve Message Opens - `postmark-pp-cli opens list` — Opens for all messages **senders** — Manage senders - `postmark-pp-cli senders create` — Create a Sender Signature - `postmark-pp-cli senders delete` — Delete a Sender Signature - `postmark-pp-cli senders get` — Get a Sender Signature - `postmark-pp-cli senders list` — List Sender Signatures - `postmark-pp-cli senders request-new-dkim` — Requests a new DKIM key to be created. - `postmark-pp-cli senders resend-confirmation` — Resend Signature Confirmation Email - `postmark-pp-cli senders update` — Update a Sender Signature - `postmark-pp-cli senders verify-spf` — Request DNS Verification for SPF (deprecated by Postmark) **server** — Manage server - `postmark-pp-cli server get` — Get Server Configuration - `postmark-pp-cli server update` — Edit Server Configuration **servers** — Manage servers - `postmark-pp-cli servers create` — Create a Server - `postmark-pp-cli servers delete` — Delete a Server - `postmark-pp-cli servers get` — Get a Server - `postmark-pp-cli servers list` — List servers - `postmark-pp-cli servers update` — Edit a Server **stats** — Manage stats - `postmark-pp-cli stats bounces` — Get bounce counts - `postmark-pp-cli stats click-browsers` — Get browser usage by family - `postmark-pp-cli stats click-locations` — Get clicks by body location - `postmark-pp-cli stats click-platforms` — Get browser plaform usage - `postmark-pp-cli stats clicks` — Get click counts - `postmark-pp-cli stats open-clients` — Get email client usage - `postmark-pp-cli stats open-platforms` — Get email platform usage - `postmark-pp-cli stats open-read-times` — Open counts by read time (seconds spent reading) - `postmark-pp-cli stats opens` — Get email open counts - `postmark-pp-cli stats overview` — Get outbound overview - `postmark-pp-cli stats sends` — Get sent counts - `postmark-pp-cli stats spam` — Get spam complaints - `postmark-pp-cli stats tracked` — Get tracked email counts **streams** — Manage streams - `postmark-pp-cli streams archive` — Archive a message stream (purged 45 days later unless unarchived) - `postmark-pp-cli streams create` — Create a message stream - `postmark-pp-cli streams get` — Get one message stream - `postmark-pp-cli streams list` — List message streams on this server - `postmark-pp-cli streams unarchive` — Restore an archived message stream before its purge date - `postmark-pp-cli streams update` — Edit a message stream **suppressions** — Manage suppressions - `postmark-pp-cli suppressions create` — Suppress up to 50 addresses on a message stream - `postmark-pp-cli suppressions delete` — Remove up to 50 suppressions from a message stream (SpamComplaint suppressions cannot be removed) - `postmark-pp-cli suppressions list` — List suppressed addresses on a message stream **templates** — Manage templates - `postmark-pp-cli templates create` — Create a Template - `postmark-pp-cli templates delete` — Delete a Template - `postmark-pp-cli templates get` — Get a Template - `postmark-pp-cli templates list` — Get the Templates associated with this Server - `postmark-pp-cli templates push-between-servers` — Push templates from one server to another - `postmark-pp-cli templates update` — Update a Template - `postmark-pp-cli templates validate` — Test Template Content **webhooks** — Manage webhooks - `postmark-pp-cli webhooks create` — Create a webhook - `postmark-pp-cli webhooks delete` — Delete a webhook - `postmark-pp-cli webhooks get` — Get one webhook - `postmark-pp-cli webhooks list` — List webhooks on this server - `postmark-pp-cli webhooks statistics` — Delivery statistics for one webhook over the last 24 hours - `postmark-pp-cli webhooks update` — Edit a webhook (omitted triggers stay unchanged) - `postmark-pp-cli webhooks verify` — Send a test request for each enabled trigger and record verified or unverified ### Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: ```bash postmark-pp-cli which "" ``` `which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query. `--json` (and other machine formats) keep that exit-2 contract and write `{"matches":[]}` on stdout so agents can inspect the envelope without treating a miss as success. ## Hand-written Extensions These commands are hand-written on top of the generated endpoint commands. They follow the same output flags (`--json`, `--agent`, `--select`, `--csv`) and the global `--server ` and `--sandbox` flags. Server tokens are masked in every response. - `postmark-pp-cli diagnose [email]`: one recipient's recent messages, bounces, and suppressions with a verdict (delivered, sent, bounced, suppressed, spam_complaint, queued, not_found) and the next command to run. `--all-servers` checks every server. - `postmark-pp-cli overview`: every server in the account with this window's sends, bounces, spam complaints, and stream count. - `postmark-pp-cli servers tokens [name]`: print the full API token for one server or all servers; the only command that reveals tokens, never cached or stored, and not exposed over MCP. - `postmark-pp-cli servers use [name]`: save the default server and optional default sender and stream for send commands. - `postmark-pp-cli templates pull `: write every template and layout to disk in the official postmark-cli folder layout, with no template cap. - `postmark-pp-cli templates push `: diff a template folder against the server; prints the plan unless `--yes` is given, and `--prune --yes` removes templates missing locally only after every local template was pushed. - `postmark-pp-cli templates render [alias]`: render one template (remote or from a pulled folder) with its layout and test model. - `postmark-pp-cli suppressions check `: whether an address is suppressed on each message stream, with the command that removes it (SpamComplaint suppressions cannot be removed). - `postmark-pp-cli bounces reactivate`: plan reactivation of inactive, reactivatable bounces filtered by type, domain, email, window, and `--stream` (default outbound); `--yes` reactivates them. - `postmark-pp-cli bounces resend-blocked`: plan resending messages that hard-bounced, to the bounced recipient only, on `--stream` (default outbound); `--send` reactivates and resends. - `postmark-pp-cli webhooks health`: 24-hour delivery statistics and verification status for each webhook, flagging failures. - `postmark-pp-cli domains health`: DKIM, Return-Path, and sender confirmation status with the fix command for each failure. - `postmark-pp-cli streams health`: bounce and spam rates per message stream against the 10% and 0.1% thresholds. - `postmark-pp-cli service-status`: Postmark's public status page, current state and open notices. The generated `email send`, `send-with-template`, `send-batch`, `send-batch-with-templates`, and `send-bulk` commands print the request they would make unless `--send` is given. `--sandbox` validates a send with Postmark's POSTMARK_API_TEST token and never delivers. For the hand-written commands, `--dry-run` only confirms the command resolves. To see what one would do, run it without `--send`, `--apply`, or `--yes`: `email send-once`, `bounces resend-blocked`, `servers bootstrap`, `templates push`, and `bounces reactivate` print their plan and change nothing until given that flag. `sync --full` never prunes here, so messages Postmark has expired and rows synced from other servers stay in the local archive. `--no-prune=false` is refused; to start a fresh archive, sync into a new file with `--db `. Syncing a different server into the same database resets the sync checkpoints and reads that server from the beginning, without pruning. Syncs into one database take turns. If `email send-once` cannot tell whether Postmark accepted a message (a timeout or a 5xx), it keeps the key reserved for the window and later runs report `delivery_unknown` instead of sending again. Over MCP, `postmark_execute` returns a preview instead of calling the API for every DELETE and for data removals, stream archives, suppression deletes, and template pushes between servers, unless the call includes `confirm: true`. ## Recipes ### Monday health pass ```bash postmark-pp-cli pulse --window 7d --baseline 28d --agent ``` Compares each server's last week against its prior four and lists anything that stopped, dropped, or spiked. ### Why didn't they get the reset email ```bash postmark-pp-cli diagnose jane@example.com --server "Staging" --agent ``` Checks outbound messages, bounces, and suppressions for one address and returns a verdict with the fix command. ### Narrow a big message search ```bash postmark-pp-cli messages list --recipient jane@example.com --count 50 --offset 0 --agent --select MessageID,Subject,Status,ReceivedAt ``` Keeps only the fields an agent needs from a large outbound search response. ### One-time code without double sends ```bash postmark-pp-cli email send-once --key otp-4821 --server "Production" --from app@example.com --to jane@example.com --subject "Your code" --text "Code: 4821" ``` Prints the payload and dedupe decision; add --send to deliver, and a retry with the same key returns the original MessageID. ### Gate template changes in CI ```bash postmark-pp-cli templates check --dir ./templates --server "Production" ``` Validates every template and layout in a pulled folder and exits non-zero on any failure. ### Spin up email for a new project ```bash postmark-pp-cli servers bootstrap "Lumen" --domain lumen.example.com --broadcast-stream --agent ``` Prints the server, stream, and domain plan with the Return-Path DNS record; the DKIM record appears after --apply creates the domain, and a rerun never duplicates the server. ## Auth Setup Postmark has two kinds of token. A server token (`X-Postmark-Server-Token`) covers one server: sending, messages, bounces, templates, stats, streams, suppressions, and webhooks. The account token (`X-Postmark-Account-Token`) covers servers, domains, sender signatures, template pushes between servers, and data removals. The CLI sends only the header each endpoint accepts. The simplest setup is the account token alone. Set `POSTMARK_ACCOUNT_TOKEN`, choose a server with `--server ` or `POSTMARK_SERVER`, and the CLI looks up that server's token through the account API. `servers use ` saves a default server. If you only use one server, export `POSTMARK_SERVER_TOKEN` instead, or store it with `auth set-token`, which reads the token from stdin. `--server` and `POSTMARK_SERVER` take precedence over `POSTMARK_SERVER_TOKEN`, which takes precedence over the saved default. `--sandbox` swaps in Postmark's `POSTMARK_API_TEST` token, so sends are validated but never delivered. Run `postmark-pp-cli doctor` to verify setup. ## Agent Mode Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color`. Global format fla