# Email

> What a customer manages in the client panel's Email and Forwarders sections, how they move a domain's mail to another provider, and what stays with you.

Source: https://www.corepanel.net/docs/client-panel/email/
Last updated: 2026-10-17
Part of the CorePanel documentation — https://www.corepanel.net/docs

---

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.

## What the customer manages

- **[Mailboxes](https://www.corepanel.net/docs/email/mailboxes)** — create and delete them, set their size, change
  their password, suspend one, and per mailbox its
  [aliases](https://www.corepanel.net/docs/email/mailboxes#forwarders),
  [autoresponder](https://www.corepanel.net/docs/email/mailboxes#autoresponder),
  [filters](https://www.corepanel.net/docs/email/mailboxes#filters) and the
  [settings to connect a phone or mail app](https://www.corepanel.net/docs/email/mailboxes#connecting-a-mail-client).
- **[Forwarders, catch-all and whole-domain redirect](https://www.corepanel.net/docs/email/mailboxes#forwarders)**,
  on their own page next to it.

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`.

## Where mail is delivered

A customer who moved to Google Workspace or Microsoft 365 sets **Email delivery → With
another provider** ([details](https://www.corepanel.net/docs/email/mailboxes#where-the-domains-mail-is-delivered)).
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](https://www.corepanel.net/docs/email/mailboxes#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".](https://www.corepanel.net/_astro/client-panel-mail-routing-light.k0u_z1-g.png)

![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.](https://www.corepanel.net/_astro/client-panel-mail-routing-dialog-light.DoJMJxD2.png)

## What stays with you

- **Anti-spam.** The [thresholds and allow/deny lists](https://www.corepanel.net/docs/email/antispam) 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](https://www.corepanel.net/docs/client-panel/websites#dns). SPF is the
  exception: they edit it with **DNS → Choose who sends my email**.