Configure Stalwart domains, accounts, and mail clients
Separate DNS readiness, mailbox authentication, and SMTP submission while enabling only the protocols the deployment needs.
Reviewed
Stalwart supports multiple client protocols, including JMAP and IMAP, alongside SMTP. Enable the protocols your users/application actually require; protocol breadth is not a reason to expose every listener.
Configure one test account
- Use the domain/directory steps in Stalwart’s setup documentation to create or connect the account source.
- Publish the exact generated domain/DKIM records and approved MX change. Review SPF, DMARC, and discovery records against the actual sending/client design.
- Configure certificates for the advertised hostnames and constrain administrative roles/network access.
- Connect a controlled client using the selected IMAP/JMAP and authenticated SMTP settings. Do not pass an admin credential to a normal mailbox client.
An account existing in an external directory does not prove the server can authenticate it or locate the correct mailbox. Check the directory mapping and permissions for the installed release.
Prove separate outcomes
Test incoming mail to the correct account, mailbox retrieval, and an approved outgoing message. Retain the server’s identifiers/log evidence and verify unknown-recipient and unauthorized-relay rejection.
Do not weaken TLS verification when autodiscovery points a client at the wrong name. Correct DNS/certificate configuration instead. A mailbox/JMAP integration also differs from MailKite’s signed incoming-event contract; design authentication and application handling for the interface you actually choose.