List a mail service's queued messages
Lists up to 100 messages in a Postfix queue, or in Stalwart's through its API, with their sender, recipients, the remote server's last reply, when the server tries again and how many attempts it has made. Requires the developer role, because it shows addresses.
Authorization
cloady Personal API token (cldy_…)
In: header
Path Parameters
Query Parameters
Value in
- "production"
- "preview"
- "development"
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/workspaces/string/apps/string/services/string/mail/queue"{ "at": 0, "messages": [ { "id": "string", "queue": "string", "arrival": 0, "size": 0, "sender": "string", "recipients": [ { "address": "string", "reason": "string" } ], "next": 0, "tries": 0 } ], "total": 0, "notes": [ "string" ]}Read a mail service's delivery GET
Reads a Postfix service's delivery log and queue: outbound attempts by outcome per step, time to delivery, inbound rejections and authentication failures, outcomes by recipient domain, bounce reasons with addresses masked, the queue's size by state and the retry settings. Postfix must log to standard output (`maillog_file = /dev/stdout`). Stalwart is read from its own Prometheus exporter and JMAP API once its admin turns the exporter on and the app holds an API key as the variable STALWART_API_KEY (and the exporter's login, if it has one, as STALWART_METRICS_AUTH, written user:secret); Mailpit and MailHog report what they caught. Nothing is invented for a server Monitor cannot read.
Retry queued mail now POST
Asks Postfix to attempt delivery now, for one queued message (`postqueue -i`) or the whole queue (`postqueue -f`), instead of waiting for its retry time. Requires the developer role.