Private Email IMAP Settings: Hosted Mailbox Configuration

Private Email is Namecheap's hosted mailbox service. Similar branded products exist from other registrars (Hostinger Business Email, GoDaddy Email, etc.) and the IMAP/SMTP setup is similar across them — but the specific hostnames and a few configuration quirks differ enough that getting the settings exactly right matters.

This guide covers Namecheap Private Email specifically (the most common search target) plus general guidance for other hosted mailbox providers.

Namecheap Private Email settings

Setting	IMAP	SMTP	POP3
Host	mail.privateemail.com	mail.privateemail.com	mail.privateemail.com
Port (SSL/TLS)	993	465	995
Port (STARTTLS)	143	587	—
Username	Full email address	Full email address	Full email address
Password	Mailbox password	Mailbox password	Mailbox password

Recommended: Use IMAP on port 993 (SSL) for receiving and SMTP on port 465 (SSL) for sending. Both are encrypted from the first byte.

Use STARTTLS (143/587) only if your client requires it.

Client-specific configuration

Outlook for Windows / Mac

1. File → Add Account → Manual setup
2. Select IMAP
3. Incoming: mail.privateemail.com / 993 / SSL/TLS
4. Outgoing: mail.privateemail.com / 465 / SSL/TLS
5. Username: full email address
6. Password: mailbox password
7. Test connection before finishing

If autodiscover fails (common with Namecheap), use Advanced/Manual setup.

Apple Mail

1. Mail → Add Account → Other Mail Account
2. Enter name, email, password
3. When asked, select IMAP type
4. Incoming: mail.privateemail.com
5. Outgoing: mail.privateemail.com
6. Apple Mail typically picks the correct ports automatically (993/465)

Thunderbird

1. Account → Add Mail Account
2. Enter name, email, password
3. Click "Configure manually"
4. Incoming: IMAP / mail.privateemail.com / 993 / SSL/TLS / Normal password
5. Outgoing: SMTP / mail.privateemail.com / 465 / SSL/TLS / Normal password

iOS Mail

1. Settings → Mail → Accounts → Add Account → Other
2. Add Mail Account
3. Enter name, email, password, description
4. Select IMAP
5. Incoming Host: mail.privateemail.com / username: full email / password
6. Outgoing Host: mail.privateemail.com / username: full email / password
7. iOS sets ports correctly when SSL is enabled in the verification dialog

Android Mail

1. Settings → Add Account → Personal (IMAP)
2. Enter email and password
3. Manual setup → IMAP
4. Incoming: mail.privateemail.com / 993 / SSL/TLS
5. Outgoing: mail.privateemail.com / 465 / SSL/TLS

Sending limits

Namecheap Private Email has per-mailbox sending limits:

Plan	Daily limit	Hourly limit
Starter	100 messages/day	30 messages/hour
Pro	300 messages/day	100 messages/hour
Ultimate	500 messages/day	200 messages/hour

These limits make Private Email unsuitable for bulk marketing or transactional volume. For higher throughput, use a transactional ESP like Postmark or SendGrid. See SMTP settings reference for ESP options.

Practitioner note: I see clients try to use Namecheap Private Email for marketing automation tools because it's cheap. It almost always ends with rate limit errors and partial sends. If you're sending more than 50 messages per day from a hosted mailbox, you've outgrown it — move sending to a dedicated transactional service and keep Private Email for your team's actual mailbox needs.

Other hosted mailbox providers

Provider	IMAP host	SMTP host
Hostinger Business Email	imap.hostinger.com:993	smtp.hostinger.com:465
Zoho Mail	imap.zoho.com:993	smtp.zoho.com:465
Fastmail	imap.fastmail.com:993	smtp.fastmail.com:465
ProtonMail (via Bridge)	127.0.0.1:1143	127.0.0.1:1025
iCloud	imap.mail.me.com:993	smtp.mail.me.com:587
Yandex Mail	imap.yandex.com:993	smtp.yandex.com:465

Settings patterns are similar; hostnames and authentication methods vary. ProtonMail uniquely requires the Bridge desktop app for IMAP/SMTP — you can't connect to ProtonMail's servers directly with standard clients.

DNS requirements

Beyond client config, your domain's DNS must point at the provider for inbound mail. For Namecheap Private Email:

example.com.    MX  10  mx1.privateemail.com.
example.com.    MX  10  mx2.privateemail.com.
example.com.    TXT     "v=spf1 include:spf.privateemail.com ~all"

Plus DKIM CNAMEs the provider gives you, and a DMARC record. See DNS records for email for the complete record list.

Common Private Email problems

Connection refused on port 993. Check that SSL/TLS is selected, not STARTTLS. The two are incompatible — port 993 is implicit SSL.

Authentication failed. Username must be the full email address, not just the local part. Common mistake: entering john instead of [email protected].

Outgoing mail rejected with "relay denied." Outgoing server requires the same authentication as incoming. Many clients store SMTP password separately — check that SMTP is also configured with credentials.

Outlook autodiscover fails. Skip autodiscover and use manual setup. Namecheap's autodiscover doesn't reliably work with Outlook 2019+ in many cases.

iOS shows "cannot verify server identity." The TLS certificate on mail.privateemail.com is valid but Apple's verification sometimes fails on first connection. Trust the certificate when prompted; subsequent connections work fine.

Mail goes to spam at Gmail. Hosted mailbox provider IP reputation can be uneven. Configure SPF, DKIM, and DMARC properly via your DNS — see SPF setup and the DMARC setup guide.

Practitioner note: Namecheap Private Email and similar consumer-grade hosted providers ship behind shared IPs with mixed reputation. If you care about reaching the inbox for important mail (sales, customer service), this is one of the strongest arguments for moving to Google Workspace or Microsoft 365 — both have significantly cleaner IP reputation.

When to upgrade

If you're using Private Email or another hosted mailbox provider and hitting any of these:

• More than 100 outbound messages/day per mailbox regularly
• Repeated deliverability complaints from recipients
• Need for advanced features (shared mailboxes, calendar, drive integration)
• Compliance requirements (HIPAA, archival)

Consider migrating to Google Workspace or Microsoft 365. For pure transactional sending, route through a dedicated SMTP service like Postmark, Mailgun, or Amazon SES.

If you're configuring hosted mailbox settings or migrating away from a hosted setup to a stronger sending stack, book a consultation. Mailbox configuration and migration is a common engagement.

Sources

• Namecheap — Private Email General Configuration
• RFC 8314: Use of TLS for Email Submission and Access
• Hostinger — Email Settings Documentation
• Zoho Mail — IMAP Configuration
• Microsoft — Server Settings for Your Email Provider
• Google Workspace — IMAP/POP Configuration

---

v1.0 · May 2026