# Set up Premium Email
Source: https://docs.webgee.com/en/premium-email/getting-started



Getting Premium Email working is four steps, and **the order matters**. Mail
cannot reach a mailbox that DNS has not yet pointed at WebGee, so creating
mailboxes first means sitting and waiting anyway.

## 1. Publish the DNS records [#1-publish-the-dns-records]

Open the **DNS Guide** tab and add every record it lists at whichever DNS
provider your nameservers point to.

The **MX** record is what actually routes mail. The **SPF**, **DKIM** and
**DMARC** records are what stop it being filed as spam once it arrives, and the
two **CNAME** records are what let mail apps configure themselves.

Full detail: [DNS records for Premium Email](/en/premium-email/dns-records).

<Callout type="warn">
  Publish the records where your nameservers actually point. If your domain is
  registered with one company and using another's nameservers, adding records at
  the registrar changes nothing. Check
  [Check what nameservers your domain uses](/en/domains-dns/how-do-i-check-what-nameservers-my-domain-is-using)
  if you are not sure which that is.
</Callout>

DNS changes take up to **24–48 hours** to propagate. Use **Check DNS** on the
tab to see WebGee's own view of your current records rather than guessing.

## 2. Create your mailboxes [#2-create-your-mailboxes]

Once the MX record resolves, open **Mailboxes** and add an account for each
person or function you need — see
[Manage mailboxes](/en/premium-email/mailboxes).

Use the panel's **Generate** button for passwords rather than choosing your own.
The password is shown once, at creation, and you will need it in step 4.

## 3. Bring old mail across, if there is any [#3-bring-old-mail-across-if-there-is-any]

If these addresses already exist at another provider, copy their contents in
**before** you tell anyone to switch. The **Email Migrator** connects to the old
server over IMAP and syncs messages across on a schedule — see
[Import mail from another provider](/en/premium-email/email-migrator).

Migrate **before** the MX cutover, not after. Once WebGee is receiving, the old
mailbox stops getting new mail, but everything already in it stays where it is
until you copy it.

## 4. Connect your mail apps [#4-connect-your-mail-apps]

Give each person their address and password, then point them at
[Connect your mail app](/en/premium-email/client-setup).

If the `autoconfig` and `autodiscover` CNAME records from step 1 have
propagated, most clients need only the address and password — they find the rest
themselves.

## Checking it works [#checking-it-works]

Before telling anyone to switch:

1. Use **Open Webmail** and sign in as one of the new mailboxes.
2. Send a message from it to an outside address, and confirm it arrives.
3. Reply from that outside address, and confirm it lands in webmail.

Both directions working means MX and SPF are right. If sending works but
receiving does not, the MX record has not propagated. If receiving works but
your mail lands in spam, the SPF or DKIM record is missing or wrong — recheck
them with **Check DNS**.

## Related [#related]

* [DNS records for Premium Email](/en/premium-email/dns-records)
* [Manage mailboxes](/en/premium-email/mailboxes)
* [Why your email is marked as spam](/en/email/why-are-my-emails-being-marked-as-spam)