Plan Hestia email for a WordPress Multisite network

WordPress Multisite lets one installation serve several sites. Hestia can host the web application, DNS, and mail, but those pieces still need to be configured separately for each domain.

Separate site domains from mail domains

A mapped site domain tells browsers where to find a subsite. An MX record tells mail systems where to deliver messages for that domain. Configure both when a mapped domain also needs its own mailbox.

Hestia provides DNS templates for local mail and for external providers such as Google Workspace, Microsoft 365, and Zoho. Pick the template that matches where the mailbox actually lives, then verify every record before changing live delivery.

Test each mailbox on its own

For each domain:

1. Create the mail domain and mailbox in Hestia, or create it with the external provider.
2. Publish the provider's MX, SPF, DKIM, and DMARC records.
3. Send and receive through webmail.
4. Add the working account to PressedMail with its IMAP and SMTP values.

Keep access intentional

People rarely need every mailbox in a Multisite network. Connect the accounts required for each person's role, and use WordPress permissions to control who can add accounts or change shared settings.

See custom IMAP and SMTP setup for the PressedMail side of the connection.