Connect maddy authentication to mailbox storage

In maddy, the authentication module and storage backend are separate components. A password entry does not automatically prove a mailbox exists or that SMTP delivery routes to it.

Configure both account layers

1. Review the authentication and storage modules linked from maddy’s reference.
2. Choose the credential source and the intended IMAP/local delivery store. Respect the project’s beta-storage warning before committing important mailboxes.
3. Provision a controlled test identity in every required layer using the installed release’s account commands.
4. Wire the SMTP pipeline’s local destination to the correct store and configure the client listener/TLS identity.

Use maddy help and the version-matched setup instructions to inspect account-management syntax; do not assume commands from a different backend apply. Keep database files, blobs, and their configuration associated in backups.

Verify the complete path

Test valid/invalid credentials, delivery to the intended address, authorized retrieval, and isolation from another account. If authentication works but mail does not appear, inspect storage provisioning and routing rather than resetting the password repeatedly.

If selecting Dovecot or another external store, use the documented SMTP/LMTP handoff and test that failure remains recoverable. maddy is not a MailKite-compatible HTTP API merely because both can accept SMTP. Application parsing, signatures, and agent execution require their own deliberate integration.