Service - Email - Poste.io (Archived)

Service - Email - Poste.io (Archived)

This page is archived. Poste.io was the recommendation circa 2022-2023. The community now runs Stalwart on 46.110.152.206 for user mailboxes and uses Cloudflare Workers send_email for application transactional mail. See:

• Self-Hosted Mail Server (2026) — current architecture, SSO integration, Stalwart vs Mailcow vs Mailu vs Mox comparison, Cloudflare options.
• apps/teamco/docs/EMAIL_SETUP.md (monorepo) — runbook for transactional mail via Cloudflare Workers.

The content below is preserved for historical reference only. Poste.io remains a perfectly valid choice for simple deploys; it’s just no longer what we run.

---

SMTP + IMAP + POP3 + Antispam + Antivirus

Web administration + Web email

…on your server in ~5 minutes

https://poste.io/doc/

Server Set Up

1. Create an Instance - See Cloud Instance Setup

2. SSH Into Server

3. Mount Storage persistently - See Linux Server Storage

4. Set up a Server for Docker - See Linux Server Initial Setup

Run Poste Docker

sudo docker pull analogic/poste.io
sudo docker run --net=host -e TZ=America/New_York -v $HOME/datadrive/var/mailserver/data:/data --name "mailserver" --restart always -h "mail.irregularchat.com" -t analogic/poste.io

Ports Explained

Inbound Rules:

The following ports need to be open for incoming connections:

Ports that are opened by poste.io:

Port	Purpose
25	SMTP - processing incoming mails from remote mail servers
80	HTTP - redirect to https and authentication for Let’s Encrypt
110	POP3 - standard protocol for accessing mailbox, STARTTLS required
143	IMAP - standard protocol for accessing mailbox, STARTTLS required
443	HTTPS - access to administration or webmail client
465	SMTPS - Legacy SMTPs port
587	MSA - SMTP port used by email clients after STARTTLS and auth
993	IMAPS - IMAP with encryption from the start
995	POP3S - POP3 with encryption from the start
4190	Sieve - remote sieve settings

Why we moved off Poste.io

1. No native Authentik / OIDC SSO — required LDAP outpost or external proxy, both with MFA-bypass concerns for mail clients.
2. Resource use — Poste.io’s bundled stack runs ~500 MB RAM idle; Stalwart does the equivalent in ~150 MB.
3. Less active development in 2024-2026 vs the major competitors (Mailcow’s IdP shipped 2025-03, Stalwart 0.15+ added OAUTHBEARER, Mox arrived as a serious modern option in 2025).

If you have a Poste.io instance running and it’s stable for your use case, there’s no urgent reason to migrate. The current wiki recommends Stalwart or Mailcow for new deployments.