Plesk Email Setup: Create Mailboxes, DKIM and Spam Filtering

Step 1: Create a Mailbox in Plesk

A minute in Plesk:

1. Open Mail in the sidebar; select your domain if you host several.
2. Click Create Email Address.
3. Set the address (sales@yourdomain.in), a strong password, and the mailbox quota.
4. Optionally add forwarding and an autoresponder on the same screen.
5. Save — the mailbox exists; webmail is live immediately at yourdomain.com/webmail.

A mailbox that exists but cannot receive mail is not finished, so the sections below walk DNS verification, client apps and spam delivery in that order. The Plesk hosting plans include the mail stack on every tier, so nothing here needs a separate mail product.

Step 2: Verify DNS — MX, SPF, DKIM, DMARC

Mail arrives only when four DNS records agree, so check them in this order:

• MX — points the domain at the mail server hostname. Plesk's DNS template creates it when the domain's DNS is hosted in Plesk; if DNS lives elsewhere, add the record at that provider.
• SPF — a TXT record starting v=spf1 that authorises the server to send for the domain.
• DKIM — switch on in Mail Settings for the domain. Plesk then publishes two _domainkey TXT records that sign outgoing mail.
• DMARC — a TXT record (_dmarc) that tells receivers what to do when SPF or DKIM fail. Start with p=none to watch reports, then tighten.

You know it worked when a test message from the new address lands in the recipient's inbox, and the received headers show a passing DKIM signature. DNS changes need time to propagate — an hour is normal, a day is not unusual.

Step 3: Webmail and Client Setup (Outlook, Gmail)

Webmail needs no setup: open yourdomain.com/webmail, log in with the full email address, and Roundcube is live in the browser.

For Outlook, Gmail or a phone, add the account manually as IMAP and enter the server details yourself:

• IMAP — server mail.yourdomain.com, port 993, SSL/TLS on.
• SMTP — server mail.yourdomain.com, port 465, SSL/TLS on. Port 587 with STARTTLS works as an alternative on most Plesk servers.
• Username — the full email address, not just the part before the @.
• Password — the mailbox password you set in Step 1; authentication is required for sending.

In Outlook: File → Add Account → enter the address → choose manual IMAP setup → type the values above → Test Account Settings. In Gmail's web app, the flow is Settings → Accounts → Add another email address, then the same server values. When the test send succeeds, mail on the phone follows the same entries.

Step 4: Fixing Spam Delivery Issues

Work through the likely causes in order:

1. Records disagree — confirm SPF and DKIM pass together for the sending domain; Step 2's test headers tell you which one failed.
2. IP reputation — run an email blacklist check on the server IP; shared IPs can be listed through a neighbour's spam, and the host removes listings.
3. Sending habits — send over authenticated SMTP (port 465), keep volume steady, and avoid blasting unverified lists from a fresh mailbox.
4. Receiver feedback — ask the recipient for the bounce text or the spam-folder headers; Gmail's "show original" names the failing check.

If records pass and the IP is clean and mail still lands in spam, publish DMARC reports for a week to see which provider objects. Mail that outgrows the plan's mailbox limits moves naturally to dedicated business email hosting.

Plesk vs cPanel Email (Comparison Table)

Comparable features, different ergonomics:

The stack underneath is the same protocol family — IMAP 993, SMTP 465, SPF/DKIM/DMARC — so skills transfer between the two panels. Choose by the rest of the server: Plesk where .NET or Windows-adjacent work lives, cPanel for Linux/WordPress fleets.