Both sides previous revision Previous revision | |
docker_notes:docker-mailserver [2024-05-11 Sat wk19 08:41] – [Docker mailserver] baumkp | docker_notes:docker-mailserver [2024-05-11 Sat wk19 08:43] (current) – baumkp |
---|
{{tag>linux docker mail mailserver Alpine dovecot postfix sqlite s6 s6-rc}} | {{tag>linux docker mail mailserver Alpine dovecot postfix sqlite s6 s6-rc}} |
======Docker mailserver====== | ======Docker mailserver====== |
This mailserver setup follows Workaround's [[https://workaround.org/ispmail-bookworm/|SPmail guide for Debian 12 “Bookworm”]]. Key changes are that instead of installing on Debian 11 virtual machine<sup>1</sup>, with a Maria mysql database<sup>2</sup>, this setup is for installation on latest Alpine linux Docker image with s6-rc init using sqlite database. | This mailserver setup follows Workaround's [[https://workaround.org/ispmail-bookworm/|SPmail guide for Debian 12 “Bookworm”]]. Key changes are that instead of installing on Debian 11 virtual machine<sup>1</sup>, with a Maria mysql database<sup>2</sup>, this setup is for installation on latest Alpine linux Docker image with s6-rc init using maria database. I toyed with sqlite and basically got it functional, however the support apps do not function with sqlite. |
| |
//As this follows Workaround's [[https://workaround.org/ispmail-bookworm/|SPmail guide for Debian 12 “Bookworm”]], significant amounts of text have been copied and generally modified from there. **I hereby credit Workaround's author Christoph Haas.** Furthermore Christoph's guide is very descriptive and should be referenced to get a better understanding of how to put together a mailserver.// | //As this follows Workaround's [[https://workaround.org/ispmail-bookworm/|SPmail guide for Debian 12 “Bookworm”]], significant amounts of text have been copied and generally modified from there. **I hereby credit Workaround's author Christoph Haas.** Furthermore Christoph's guide is very descriptive and should be referenced to get a better understanding of how to put together a mailserver.// |
- The database requirements for a small mailserver with a few dozen domains, with each domain having hundreds of emails and aliases is well within the capacity of the sqlite database. The use of a full multi user server / client relational database is not necessary, particularly for a Docker based server implementation. See [[https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgresql-a-comparison-of-relational-database-management-systems|SQLite vs MySQL vs PostgreSQL: A Comparison Of Relational Database Management Systems]] | - The database requirements for a small mailserver with a few dozen domains, with each domain having hundreds of emails and aliases is well within the capacity of the sqlite database. The use of a full multi user server / client relational database is not necessary, particularly for a Docker based server implementation. See [[https://www.digitalocean.com/community/tutorials/sqlite-vs-mysql-vs-postgresql-a-comparison-of-relational-database-management-systems|SQLite vs MySQL vs PostgreSQL: A Comparison Of Relational Database Management Systems]] |
| |
I got the Docker emailer server functional mid 2023. It still needs some more work. Currently I run the mail server 2 containers, I would rather have it all in one container. The email server could also have some more optimisations performed. | <fc #008000>I got the Docker emailer server functional mid 2023. It still needs some more work. Currently I run the mail server 2 containers, I would rather have it all in one container. The email server could also have some more optimisations performed. |
| </fc> |
=====Dockerfile===== | =====Dockerfile===== |
I go annoyed with the messy UID and GID and found this reference to attempt to standardise upon. <fc #ffa500>//Sadly there seems to be no comprehensive standard!//</fc> | I go annoyed with the messy UID and GID and found this reference to attempt to standardise upon. <fc #ffa500>//Sadly there seems to be no comprehensive standard!//</fc> |