Skip to content
HostPora
Emailintermediate3 min read

Configure a Mailbox and Email Authentication

Create a mailbox, use encrypted device settings and publish SPF, DKIM and DMARC records without breaking existing senders.

Written by HostPora Academy Team · Technical review by HostPora Technical Review · Updated Nov 2, 2026

Step 1

Create and protect the mailbox

Use a unique password, record the exact username and apply the incoming and outgoing server names shown by the hosting service.

  1. 1Use encrypted IMAP
  2. 2Use authenticated SMTP
  3. 3Avoid shared passwords
Step 2

Publish authentication records

SPF lists approved sending systems, DKIM signs messages and DMARC states how receivers should handle failed alignment.

  1. 1Inventory every sender
  2. 2Enable DKIM
  3. 3Start DMARC with reporting
Step 3

Test real delivery

Send to multiple external providers, review headers and confirm replies return to the expected mailbox.

  1. 1Check spam placement
  2. 2Inspect authentication results
  3. 3Test password reset mail

Did this guide solve the task?

Your response helps prioritize corrections and missing steps.

Thanks. Your feedback will guide the next article review.

Common questions

Resolve the details before changing production.

Can I publish two SPF records?+

No. Combine approved senders into one SPF policy for the hostname.

Should DMARC start with reject?+

Start with monitoring when you have not inventoried every sender, then strengthen the policy after reviewing reports.

Why does receiving work while sending fails?+

Incoming and outgoing mail use different servers, ports and authentication. Verify SMTP settings and network restrictions.

Ready when you are

Find the hosting that fits your next move.

Compare resources, full-term totals and renewals before you choose. WHMCS handles checkout and billing.

Built for the tools websites and applications use

cPanel DirectAdmin LiteSpeed Softaculous WordPress Node.js Laravel Python PHP MySQL MariaDB NGINX Linux Drupal Joomla NVMe Cloudflare Let's Encrypt

Availability varies by plan and operating environment. Product names belong to their respective owners.