Early Black Friday: 20% off all our plans, whatever the billing period, with code BLACKFRIDAY20. Until 1 December. See the plans →

Set up your email: mailboxes, DNS, MX and webmail

Published on 21/08/2026 Updated on 21/11/2026 696 views
Hébergement Web E-mail IMAP DNS MX Webmail

Creating a mailbox and directing incoming mail to it are separate steps. Your website can work while your MX records still point to an old provider.

Examples use only example.com and the placeholder HOSTING_IP. Replace them with your domain and your mail hosting IPv4 address; do not publish the placeholders unchanged.

Create the mailbox and find its settings

Open My services → your web hosting → Emails. Create the address, choose a long, unique password and check your plan’s limits. Sign in with the mailbox’s complete email address and its own password, not your client account credentials.

Find the server information on your hosting page or in Plesk. Use the IP and settings belonging to this hosting service, not an unrelated VPS. If the mail server IP is unclear, ask Support.

Where should you edit DNS?

Edit the zone at the provider serving the domain’s nameservers (NS). Your registrar and DNS provider may differ. With external nameservers, changing a zone copy at By-Hoster does not change public DNS.

You do not need to transfer your domain or change its nameservers to edit MX records: DNS zone guide and externally managed domains.

Which mail and webmail records are required?

To use the email service on your By-Hoster hosting, adapt this table to your service’s actual settings:

Type Name Value Priority
A mail HOSTING_IP —
A webmail HOSTING_IP —
MX @ mail.example.com. 10

In DNS editors, @ usually means the domain itself; some require example.com. The names mail and webmail may need to be entered in full. An MX target must be a hostname, not an IP or URL, with an A record pointing to the mail server.

If moving all incoming mail to By-Hoster, replace the old MX records with the required new ones. Do not mix providers’ MX records to split mailboxes. If retaining third-party email, keep that provider’s MX records. Leave unrelated website and service records unchanged.

With Cloudflare, the mail hostname used for SMTP must be DNS only, without the HTTP proxy.

Use webmail or an email client

Once DNS resolves, open https://webmail.example.com using your mailbox credentials. Its certificate must cover that hostname. If it does not, use your hosting’s SSL / HTTPS management after correcting DNS, or contact Support. Do not bypass a certificate warning: HTTPS guide.

For Outlook, Thunderbird or mobile, copy the server and ports actually shown under Emails. Depending on the server, these may include IMAP 993 with SSL/TLS, POP3 995 with SSL/TLS, SMTP 465 with SSL/TLS or 587 with STARTTLS. Use only the options available for your hosting. SMTP requires authentication with the complete address and mailbox password. IMAP synchronises folders; with POP3, keeping messages on the server depends on client settings.

Check SPF, DKIM and DMARC

MX routes incoming mail; it does not by itself authorise outgoing messages.

  • SPF: publish a single SPF TXT record at the domain root covering all authorised senders. For example, v=spf1 ip4:HOSTING_IP ~all is suitable only after replacing the placeholder with the confirmed sending IP, if it is your sole sending source. Preserve required authorisations for other senders.
  • DKIM: enable signing in Plesk’s mail settings, then copy the supplied public key and selector name into the authoritative DNS zone. Do not invent a key.
  • DMARC: configure _dmarc after checking SPF/DKIM and legitimate senders. A strict rejection policy introduced too early can reject your own mail.

Verify the result and troubleshoot

dig +short example.com NS
dig +short example.com MX
dig +short mail.example.com A
dig +short webmail.example.com A

On Windows: nslookup -type=MX example.com, then nslookup mail.example.com and nslookup webmail.example.com.

Answers should match your settings. Caches can retain previous values for their TTL, including a previous “name not found” answer. Wait for that cache period, then test sending and receiving with another mailbox.

  • Webmail hostname not found: check the webmail A record in the authoritative zone.
  • 554 / Relay access denied on incoming mail: check MX, the domain’s configuration on the mail server and the mailbox’s existence. For outgoing mail, also check SMTP authentication.
  • Missing message: check spam, quota and the exact rejection. Previously rejected messages must be sent again.

If needed, open a ticket with the error code and DNS results, without sharing your password.

Was this article helpful?