Suspending accounts and tenants
Suspending stops someone from using their mail without deleting anything. Reactivating puts everything back as it was.
How to suspend
- One person: in the admin panel, open the tenant, find the user under Users and press Suspend (or Reactivate). Over the API:
PATCH /v1/tenants/{tenantId}/accounts/{accountId}with{"status": "suspended"}or{"status": "active"}. - A whole tenant: set the tenant's status to Suspended on its page, or
PATCH /v1/tenants/{tenantId}with{"status": "suspended"}. Every account in it is suspended with it; their own status is kept, so reactivating the tenant does not reactivate people you suspended one by one. Tenants waiting for payment (pending) behave the same way.
What happens
| Suspended | |
|---|---|
| Webmail | Signed out on the next request (open pages within 30 seconds). Signing in with the right password says the account is suspended; a wrong password just says it is wrong. |
| Mail apps (IMAP) | Open connections are closed within about 15 seconds, or after their next command. Logging in with the right password answers NO [CONTACTADMIN]. |
| JMAP apps | Refused at once; open event streams close within 15 seconds. |
| Sending (SMTP submission, webmail) | Refused. |
| Filters (ManageSieve) | Refused at the next login. |
| Incoming mail | Refused as if the address did not exist (550), so senders get a bounce. Nothing is queued for later. |
| Stored mail, folders, filters, aliases | Kept unchanged. |
| Image links in webmail | Stop working. |
Changing someone's password has the same effect on their open sessions: webmail sessions end at once and mail-app connections that logged in with the old password are closed within about 15 seconds.
Not there yet
A reason or note stored with the suspension, a date when it ends by itself, a message shown to senders, and holding incoming mail during a suspension instead of refusing it. Open ManageSieve and SMTP connections are not closed early; they are short-lived and checked at login.