Provision Mailu mailboxes, aliases, and delegated administration
Use Mailu's admin model to define domains and recipient routing while keeping mailbox credentials separate from administrative authority.
Reviewed
Mailu supplies administration and mailbox services around a containerized mail stack. Choose account ownership and alias behavior deliberately; a forwarding address is not an independently isolated mailbox.
Configure the recipient model
- Use the administration guidance for your release from Mailu’s documentation.
- Create the domain and a controlled mailbox with the intended quota and access policy.
- Create required postmaster/role aliases and review any forwarding or catch-all behavior.
- Restrict delegated administrators to their intended scope and keep global administration credentials out of application/client configuration.
Publish exact signing/authentication DNS for the configured domain. If using Mailu’s management API, verify its enabled feature, authentication, and authorization separately; it is not interchangeable with a transactional sending API.
Verify the real account path
Connect a controlled mail client using the actual IMAP/submission hostnames and trusted TLS. Test valid/invalid authentication, incoming receipt, outgoing submission, alias delivery, and rejected unknown recipients.
Check sending identity permissions and verify unauthorized clients cannot relay. Do not infer inbox delivery from an SMTP acceptance alone. To feed an application, use a supported forwarding/filtering design and authenticate the receiving boundary; Mailu does not automatically attach MailKite webhook signatures to its own messages. Keep account data and domain settings in the backup plan.