Our great sponsors
-
Mail-in-a-Box
Mail-in-a-Box helps individuals take back control of their email by defining a one-click, easy-to-deploy SMTP+everything else server: a mail server in a box.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
docker-mailserver
Production-ready fullstack but simple mail server (SMTP, IMAP, LDAP, Antispam, Antivirus, etc.) running inside a container.
Mail-in-a-Box
Mailcow
I have an internal only mail server that doesn't send or receive mail outside my LAN. I use docker-mailserver for this. It's fairly easy to set up a minimal server though I haven't figured out how to enable SSL/TLS so everything is unencrypted in the backend at the moment. I mainly expose the mail server to my other selfhosted services so they can send notification emails to users. Users access their mail through a selfhosted roundcube webmail frontend. No IMAP/SMTP ports are exposed on the LAN or externally. It's enough for my use case (to teach my kids email). The only downside for me is that it doesn't support password changes from the webmail interface natively. All administration tasks are performed using a shell script, including password changes, so only the administrator can change the password for any user. There's a third-party add-on script that enables user password changes from the web client but I haven't investigated/implemented it, so don't know how well it works. It's also possible to set up SSL/TLS encryption for IMAP/SMTP but, in my case, it's less straightforward than described in the documentation because I want to keep it strictly internal only and don't want to open any ports on my router for email. I haven't been motivated enough to poke further because the setup works well otherwise.
I have an internal only mail server that doesn't send or receive mail outside my LAN. I use docker-mailserver for this. It's fairly easy to set up a minimal server though I haven't figured out how to enable SSL/TLS so everything is unencrypted in the backend at the moment. I mainly expose the mail server to my other selfhosted services so they can send notification emails to users. Users access their mail through a selfhosted roundcube webmail frontend. No IMAP/SMTP ports are exposed on the LAN or externally. It's enough for my use case (to teach my kids email). The only downside for me is that it doesn't support password changes from the webmail interface natively. All administration tasks are performed using a shell script, including password changes, so only the administrator can change the password for any user. There's a third-party add-on script that enables user password changes from the web client but I haven't investigated/implemented it, so don't know how well it works. It's also possible to set up SSL/TLS encryption for IMAP/SMTP but, in my case, it's less straightforward than described in the documentation because I want to keep it strictly internal only and don't want to open any ports on my router for email. I haven't been motivated enough to poke further because the setup works well otherwise.
Related posts
- Mail-in-a-Box – Take back control of your email
- Roundcube and docker-mailserver (Docker Mailserver) on the same VPS
- Small business owner: considering signi g up to Microsoft Office Premium for mail etc.
- Mail-in-a-Box: a mail server in a box
- mailinabox: Mail-in-a-Box helps individuals take back control of their email by defining a one-click, easy-to-deploy SMTP+everything else server: a mail server in a box.