Configure Mail-in-a-Box users, aliases, and client access
Use appliance-managed accounts and DNS checks and distinguish mailbox identity from administrative access and alias routing.
Reviewed
Manage mailboxes through Mail-in-a-Box’s supported administrative interface, not direct edits to underlying Dovecot/Postfix data. Its status checks and generated client guidance assume the appliance owns that configuration.
Configure one mailbox safely
- Follow the account/client sections in the official guide.
- Create a controlled user and any explicitly approved alias. Review whether additional domains/addresses share an existing mailbox or form a separate identity.
- Resolve the status console’s DNS and certificate findings for the chosen domain.
- Configure a mail client using the appliance’s actual IMAP/SMTP hostnames and TLS settings, not its administrator login as an application credential.
When DNS is hosted elsewhere, reproduce all required records from the current appliance guidance and understand which future changes need manual synchronization.
Verify the user journey
Check login, controlled receipt, retrieval, and an approved authenticated send. Confirm unknown-address and unauthorized-relay behavior and inspect signing/authentication headers for the actual domain.
An alias is a delivery mapping, not a new credential or tenant boundary. If forwarding to an application address, prevent loops and avoid exposing unrelated user mail. MailKite’s SDK/webhooks are an independent application integration; Mail-in-a-Box’s mailbox and administrative interfaces do not automatically emulate that API.