Skip to content

Email

The Email section is where a customer runs the mailboxes of their own domains, and Forwarders is where they decide what happens to mail no mailbox answers. Both are the same screens you use, limited to the account’s domains.

The domain picker lists the account’s primary domain, aliases and addons. Subdomains never appear: mail for blog.example.com is mail for example.com.

A customer who moved to Google Workspace or Microsoft 365 sets Email delivery → With another provider (details). From then on, mail this server sends to that domain — contact forms, WordPress notices — follows the MX instead of landing in local mailboxes.

  • The page suggests it when the MX already points to a known provider.
  • The DNS task Use another email service switches it in the same step.
  • A domain the provider made a backup MX shows “This server is the backup MX”, and the customer cannot change it.

The client panel's Email page in Classic Blue, for the domain cp-community.org with one mailbox, hello@cp-community.org. Under the domain picker an "Email delivery" strip reads "Delivered to the mailboxes on this server" with a Change button. Below it an amber notice says "This domain's email seems to be with another provider": its MX records point to aspmx.l.google.com and two alternates, yet messages this server sends to @cp-community.org — contact forms, WordPress notices — still go to the mailboxes here. A "Deliver to that provider" button sits on its right. In the sidebar, under Email, the functions list ends with "Email routing".

The "Where is the email for cp-community.org?" dialog. It says the MX records point to aspmx.l.google.com, alt1.aspmx.l.google.com and alt2.aspmx.l.google.com, and offers two choices: "On this server" (email arrives in the mailboxes you create here) and the selected "With another provider" (Google Workspace, Microsoft 365 or another mail server; messages this server sends to @cp-community.org go there too, following the MX records). A note says the mailboxes, forwarders and catch-all are kept but stop receiving until "On this server" is chosen again. Cancel and Save buttons close it.

  • Anti-spam. The thresholds and allow/deny lists are not in the client panel. A customer losing mail to the filter asks you, and you adjust it per mailbox.
  • Email authentication. DKIM keys are generated and rotated by the server, and the customer sees them locked in DNS. SPF is the exception: they edit it with DNS → Choose who sends my email.