Suspending a mailbox
A mailbox can be stopped three ways, separately or together:
| Suspend | What stops | What keeps working |
|---|---|---|
| The mailbox | Signing in anywhere (webmail, mail apps, app passwords); it is signed out within seconds. Mail to it is refused. | Its mail, calendars and contacts are kept. |
| Incoming mail | Mail to it and its aliases is refused with 550 5.2.1 This mailbox is not accepting mail, from other servers and from mailboxes here. | Signing in, reading and sending. |
| Sending | Sending from webmail, mail apps (SMTP) and JMAP is refused with 550 5.7.1 Sending is suspended for this mailbox; its forwarding to other servers and its vacation replies stop. | Signing in, reading and receiving mail. |
Who can suspend
- The tenant's owners and admins (and members whose tenant role covers users), in the tenant manager at
/manage: People → Mailboxes → Suspension next to the mailbox. They can lift what they set. Nobody can suspend their own mailbox. - The platform's staff, from the admin panel. What staff suspend shows in the tenant manager as by the platform, and only staff can lift it or change its note. Suspending again from the tenant manager leaves it the platform's. If you think staff suspended a mailbox by mistake, open a support ticket.
Add a note saying why: it shows next to the suspension for the tenant's managers and staff.
From the API
PATCH /v1/tenants/{tenantId}/accounts/{accountId} with any of status, inbound and outbound (active or suspended) and suspensionNote. The mailbox shows suspendedBy, inboundSuspended and outboundSuspended (tenant, staff or null). A team API key asking to lift what staff set gets 403, and nothing in that request is changed.
Sending paused after complaints
Separately, a mailbox whose mail draws too many spam complaints has its mail to other servers paused automatically; only the platform's staff resume it. See the FAQ.