diff --git a/astro.config.mjs b/astro.config.mjs index 34141a8..c71c95b 100644 --- a/astro.config.mjs +++ b/astro.config.mjs @@ -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' } }], diff --git a/src/content/docs/email/set-up-your-email-client.mdx b/src/content/docs/email/set-up-your-email-client.mdx new file mode 100644 index 0000000..520c8e0 --- /dev/null +++ b/src/content/docs/email/set-up-your-email-client.mdx @@ -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. + + + +## 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. + + + +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. + + + +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 | + + + +### 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. + + + +## 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? + + diff --git a/src/content/docs/email/spam-filtering-changes.mdx b/src/content/docs/email/spam-filtering-changes.mdx new file mode 100644 index 0000000..2ca9728 --- /dev/null +++ b/src/content/docs/email/spam-filtering-changes.mdx @@ -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. + + + +## 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? + + diff --git a/src/pages/index.astro b/src/pages/index.astro index e2c6a4e..60db0b6 100644 --- a/src/pages/index.astro +++ b/src/pages/index.astro @@ -23,10 +23,10 @@ const PRODUCT_META: Record