Manage mox accounts, addresses, and client access

mox separates accounts, addresses, domains, and aliases. Adding an address is not necessarily creating a separate isolated account; choose the relationship according to who should see the mailbox contents.

Provision the intended mailbox boundary

1. Use the administration interface or supported commands in the command reference for the installed version.
2. Create a controlled account and attach the intended address/domain, or explicitly add an alias to an existing account.
3. Set credentials through the documented password operation and keep them out of arguments/logs where the tool supports secure entry.
4. Use mox’s clientconfig guidance to configure the real service hostnames and TLS modes in the client.

Check mox config account list and the documented account/address inspection tools before creating duplicates. Do not assume a second address provides tenant isolation from its owning account.

Test mailbox and delivery separately

Verify successful/failed authentication, a controlled incoming message, mailbox retrieval, and approved outgoing submission. Check that an unrelated account cannot inspect the test mailbox and that unknown recipients receive the intended SMTP response.

Client access, the optional web/API features, and application event handling have different contracts. Use the actual mox API documentation if choosing it; do not assume a Postal-like incoming route or a MailKite signature. Keep account changes in the same recovery plan as configuration and mailbox data.