docs: add Email section — client setup + Baruwa retirement notice
Replaces the three Outlook 2016 articles (WHMCS 2, 3, 9 — ~62k views) with one client-agnostic setup guide. Outlook 2016 went end of life in October 2025, and the two archiving articles documented a feature the current Outlook doesn't have. Server settings are taken from the live autoconfig endpoint rather than the old articles: IMAP 993/SSL, POP3 995/SSL, SMTP 587/STARTTLS, username is the full address. cPanel settings verified against cpanel01. Adds a Baruwa retirement notice covering the move to Proxmox Mail Gateway in November 2026. Deliberately frames this as a platform change rather than describing our current outbound filtering posture — see the PR discussion. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
AnHonestHost Dev
co-authored by
Claude Opus 5
Claude Opus 5
parent
425f364f48
commit
b00a5fd8cf
@@ -22,6 +22,7 @@ export default defineConfig({
|
||||
'/domains/': '/domains/transferring-a-domain-to-us/',
|
||||
'/support/': '/support/remote-support/',
|
||||
'/cpanel/': '/cpanel/nameservers/',
|
||||
'/email/': '/email/set-up-your-email-client/',
|
||||
},
|
||||
vite: {
|
||||
resolve: {
|
||||
@@ -96,6 +97,10 @@ export default defineConfig({
|
||||
label: 'Domains',
|
||||
items: [{ autogenerate: { directory: 'domains' } }],
|
||||
},
|
||||
{
|
||||
label: 'Email',
|
||||
items: [{ autogenerate: { directory: 'email' } }],
|
||||
},
|
||||
{
|
||||
label: 'Support',
|
||||
items: [{ autogenerate: { directory: 'support' } }],
|
||||
|
||||
@@ -0,0 +1,91 @@
|
||||
---
|
||||
title: Set up your email
|
||||
description: Connect Outlook, Apple Mail, Thunderbird, or your phone to your mailbox — with the server settings for both WHP and cPanel hosting.
|
||||
sidebar:
|
||||
order: 1
|
||||
---
|
||||
|
||||
import { Steps, Aside } from '@astrojs/starlight/components';
|
||||
import Support from '~/content/partials/support-link.mdx';
|
||||
|
||||
You can read your mail in any standard email app. Most will configure themselves once you enter your address and password — and if yours doesn't, the settings are below.
|
||||
|
||||
<Aside type="tip">
|
||||
**Just want to check your mail?** You don't need to set anything up. Webmail works in any browser with no configuration — ask us for your webmail address if you don't have it.
|
||||
</Aside>
|
||||
|
||||
## Let your app configure itself
|
||||
|
||||
Try this first. It works in most modern clients, including Outlook, Apple Mail, and the mail apps on iOS and Android.
|
||||
|
||||
<Steps>
|
||||
|
||||
1. Add a new account in your email app.
|
||||
|
||||
2. Enter your **full email address** (`you@yourdomain.com`) and its password.
|
||||
|
||||
3. Choose **Next** or **Sign in** and let the app look up the settings.
|
||||
|
||||
</Steps>
|
||||
|
||||
If the app finds everything, you're done. If it asks for server details, use the table below.
|
||||
|
||||
## Server settings
|
||||
|
||||
Use your **full email address** as the username — not just the part before the `@`. That single detail accounts for most setup failures.
|
||||
|
||||
### WHP hosting
|
||||
|
||||
| Setting | Value |
|
||||
| --- | --- |
|
||||
| **Incoming (IMAP)** | `mail01.cloud-hosting.io`, port **993**, SSL/TLS |
|
||||
| **Incoming (POP3)** | `mail01.cloud-hosting.io`, port **995**, SSL/TLS |
|
||||
| **Outgoing (SMTP)** | `mail01.cloud-hosting.io`, port **587**, STARTTLS |
|
||||
| **Username** | Your full email address |
|
||||
| **Authentication** | Required, for outgoing as well as incoming |
|
||||
|
||||
<Aside type="note">
|
||||
`mail01` is an example. Your server's mail hostname is shown in WHP on the **Dashboard** page under **Server Information**, and the **Email** page has a **Setup Instructions** button with the exact values for your account.
|
||||
</Aside>
|
||||
|
||||
### cPanel hosting
|
||||
|
||||
| Setting | Value |
|
||||
| --- | --- |
|
||||
| **Incoming (IMAP)** | `cpanel01.cloud-hosting.io`, port **993**, SSL/TLS |
|
||||
| **Incoming (POP3)** | `cpanel01.cloud-hosting.io`, port **995**, SSL/TLS |
|
||||
| **Outgoing (SMTP)** | `cpanel01.cloud-hosting.io`, port **465**, SSL/TLS |
|
||||
| **Username** | Your full email address |
|
||||
| **Authentication** | Required, for outgoing as well as incoming |
|
||||
|
||||
Port **587 with STARTTLS** also works for outgoing if your app prefers it.
|
||||
|
||||
## IMAP or POP3?
|
||||
|
||||
Choose **IMAP** unless you have a specific reason not to.
|
||||
|
||||
- **IMAP** keeps mail on the server and mirrors it to every device. Read a message on your phone and it shows as read on your laptop. This is what you want when you use more than one device.
|
||||
- **POP3** downloads mail to one device and, by default, removes it from the server. Mail then exists only on that machine — if it dies, so does your mail.
|
||||
|
||||
<Aside type="caution">
|
||||
Take care switching an existing account from POP3 to IMAP. If POP3 has been deleting messages from the server as it downloaded them, those messages exist only in your local app — and they won't reappear when you switch. Back up first, or ask us to check before you change anything.
|
||||
</Aside>
|
||||
|
||||
## Common problems
|
||||
|
||||
**Incoming works, outgoing fails.** Almost always because outgoing authentication is off. Many apps leave it unticked by default. Find the option — usually *My outgoing server requires authentication* — and enable it with the same username and password.
|
||||
|
||||
**Password rejected.** Use the full email address as the username. If it still fails, reset the mailbox password and try again — and watch for autocorrect capitalising the first letter on phones.
|
||||
|
||||
**Certificate warnings.** Connect using the server hostname in the table above, not your own domain. A certificate is issued for the server's name, so connecting as `mail.yourdomain.com` can trigger a mismatch warning even though everything works.
|
||||
|
||||
**Old mail missing after setup.** If the account was previously POP3, see the caution above before assuming anything is lost.
|
||||
|
||||
## Related
|
||||
|
||||
- [Create an email account](/whp/how-to/create-an-email-account/) — WHP
|
||||
- [Send WordPress email from your own domain](/cpanel/wordpress-email-from-your-domain/)
|
||||
|
||||
## Still stuck?
|
||||
|
||||
<Support />
|
||||
@@ -0,0 +1,53 @@
|
||||
---
|
||||
title: Changes to spam filtering
|
||||
description: We're moving spam filtering from Baruwa to Proxmox Mail Gateway. What's changing, when, and what you need to do.
|
||||
sidebar:
|
||||
order: 2
|
||||
badge: Notice
|
||||
---
|
||||
|
||||
import { Aside } from '@astrojs/starlight/components';
|
||||
import Support from '~/content/partials/support-link.mdx';
|
||||
|
||||
We're changing the platform that filters spam for our mail customers.
|
||||
|
||||
**Baruwa**, which we've used for years, reaches end of life in **November 2026** — its developers are stopping support and security updates. Rather than run mail filtering on software that no longer receives fixes, we're moving to **Proxmox Mail Gateway**.
|
||||
|
||||
## What this means for you
|
||||
|
||||
**For most customers, nothing changes and there's nothing to do.** Your address stays the same, your mailbox and its contents are untouched, and your email app keeps working without reconfiguration. Filtering continues throughout — we're changing what does it, not whether it happens.
|
||||
|
||||
If you're one of the customers who uses the Baruwa web interface directly — to review quarantined mail, or to manage your own allow and block lists — that's the part that changes, since Proxmox Mail Gateway has its own interface. **We'll contact you individually** to move you across and show you the equivalent screens. You don't need to do anything in the meantime.
|
||||
|
||||
<Aside type="tip">
|
||||
Worth doing now, whoever you are: if you've built up allow or block lists in Baruwa that matter to you, take a copy. We'll migrate what we can, but having your own record makes it easy to confirm nothing was missed.
|
||||
</Aside>
|
||||
|
||||
## Timeline
|
||||
|
||||
| When | What happens |
|
||||
| --- | --- |
|
||||
| Now | Baruwa continues to run. We begin moving customers across. |
|
||||
| Before November 2026 | Affected customers are contacted individually and migrated. |
|
||||
| November 2026 | Baruwa reaches end of life and is retired. |
|
||||
|
||||
We'll update this page as the migration progresses.
|
||||
|
||||
## Questions we expect
|
||||
|
||||
**Will I lose quarantined mail?** Anything currently held in quarantine stays available until your migration. If something in there matters, release it to your inbox rather than leaving it quarantined.
|
||||
|
||||
**Do I need to change my email settings?** No. Server names, ports, and passwords are unaffected — see [Set up your email](/email/set-up-your-email-client/) if you're configuring a new device.
|
||||
|
||||
**Is my mail less protected during the change?** No. Filtering runs continuously through the migration; there's no window where mail is unfiltered.
|
||||
|
||||
**I'd rather opt out of filtering entirely.** Talk to us and we'll go through the options and the trade-offs.
|
||||
|
||||
## Related
|
||||
|
||||
- [Set up your email](/email/set-up-your-email-client/)
|
||||
- [Create an email account](/whp/how-to/create-an-email-account/)
|
||||
|
||||
## Questions about your account?
|
||||
|
||||
<Support />
|
||||
@@ -23,10 +23,10 @@ const PRODUCT_META: Record<string, { title: string; blurb: string; firstSection:
|
||||
blurb: 'Tips and tricks for getting the most out of WordPress on WHP.',
|
||||
firstSection: 'index',
|
||||
},
|
||||
'email-clients': {
|
||||
title: 'Email clients',
|
||||
blurb: 'Configure Outlook, Apple Mail, Thunderbird, and mobile clients.',
|
||||
firstSection: 'index',
|
||||
email: {
|
||||
title: 'Email',
|
||||
blurb: 'Set up Outlook, Apple Mail, Thunderbird, and mobile clients — plus news about our filtering.',
|
||||
firstSection: 'set-up-your-email-client',
|
||||
},
|
||||
domains: {
|
||||
title: 'Domains',
|
||||
|
||||
Reference in New Issue
Block a user