gmvaultdb VS docker-mailserver

I agree, but an an alternative to mbox/maildir format on your machine : this is also why I wrote https://github.com/karteum/gmvaultdb in order to have a single-file SQLite DB with all old email contents (all UTF-8 inside, simple/minimalistic schema), together with a small GUI to consult emails and do queries (full-text not fully implemented yet but this is the target) and all attachments extracted in a side folder so that I can directly browse with a file manager.

I can recommend Docker mailserver (it also works with Podman). It is already pretty lightweight but you can even make it lighter and it has an active community as well as regular updates.

https://github.com/docker-mailserver/docker-mailserver https://docker-mailserver.github.io/docker-mailserver/latest/ https://www.programonaut.com/how-to-host-a-mail-server-with-docker-for-free-step-by-step/

Use https://github.com/docker-mailserver/docker-mailserver or mailcow . They both provide reasonable default setup for spam detection and even UI for adjusting settings.

" this docker based mail server looks pretty legit https://github.com/docker-mailserver/docker-mailserver "

Check https://github.com/docker-mailserver/docker-mailserver It has almost everything in a single docker image. Email is not the easiest to implement with container(s), but that project has managed it.

I set up docker-mailserver[0] Monday in ~6 hours, most of which were me trying to be fancy using podman instead of docker and dealing with SELinux. But then again I did choose it over mail-in-a-box for just that level of customization. Obviously I can't tell how reliable it will be in the long run yet, but since it's using the classic Postfix/Dovecot stack I expect it'll be pretty stable

[0] https://github.com/docker-mailserver/docker-mailserver