Activity & troubleshooting
Activity includes outgoing messages from the Dashboard, the mail client, the Mailbox API, direct REST, and SMTP, as well as incoming mail for this Mail project. It is a processing and local handoff history, not a mailbox or a final recipient delivery receipt. Stored mail is read in the mail client.
Read Activity
Open a Mail project’s Activity page. Use the outbound cursor to browse older sends; the API accepts before and limit and returns a next cursor. Incoming entries show the recipient alias, original sender, delivery or forwarding state, and destination results.
Outbound states
| State | Meaning | Next action |
|---|---|---|
queued / scanning | Accepted for processing or being checked. | Wait and refresh status. |
deferred | A temporary issue delayed local processing. | Inspect the reported error and allow the bounded retry path. |
handed_to_postfix | Postfix accepted the message into its local queue. | Check the recipient mailbox separately. This is not proof of remote delivery. |
failed / rejected | Validation, policy, scanner, or handoff ended the attempt. | Read the error, correct the issue, and submit a changed message with a new idempotency key. |
handoff_unknown | Mail cannot tell whether Postfix accepted the handoff. | Check history and the recipient before retrying; an automatic retry could duplicate mail. |
cancelled | A queued, deferred, or scanning message was cancelled. | Submit a new message if needed. A message already handed to Postfix cannot be recalled. |
Accepted by the local queue is the exact claim
handed_to_postfix.Inbound delivery and forwarding
When an address delivers into mailboxes, the entry shows delivered once the message is stored. When none of its mailboxes has room, because the project's storage or the mailbox caps are full, it shows deferred: the sending server keeps the message and retries, so free up space and it arrives on a later attempt. A mailbox at its cap is skipped while the address's other mailboxes still receive the message.
A forwarded message can have more than one destination. Each destination has its own forwarding result. deferred means Mail will retry within a bounded lifetime. expired means the retry count or lifetime was exhausted. handoff_unknown means Mail will not retry blindly because the destination may already have been accepted by Postfix.
Troubleshoot
| Symptom | Check |
|---|---|
| Address cannot be created | The chosen alias may already be reserved, the five-address allowance may be used, or FORWARD_DESTINATION_UNVERIFIED requires destination confirmation. |
| Inbound mail never appears | Custom-domain MX and DNS checks, exact alias spelling, enabled route, priority, and any reject or discard rule. For mailbox delivery, also check the Spam folder, blocked senders, and whether mailbox storage is full. |
| REST or SMTP send rejected | Credential type, enabled state, authorized sender, visible From/envelope match, recipient allowance, MIME format, and size policy. |
| Message is queued but not received | Read the latest activity state. For handed_to_postfix, check the recipient mailbox and its spam folder; Mail cannot confirm final placement. |
| DNS check fails intermittently | Verify each generated record separately and retry after resolver propagation. A temporary lookup failure does not by itself disable a previously working domain. |
For programmatic investigation, use Dashboard Activity or, for direct REST submissions, message status endpoint.