Mailcow-dockerized: How to cut down the size of mailcow installation?

[akash07k]

I want to know that is there any way by which I can cut down the size of mailcow installation on my docker machine?
Right now I have very limited server with only 40 gb of SSD and 1GB of RAM.
Is there any way that I do not install unwanted components such as redis and all?

[andryyy]

Please use the Telegram channel for these questions. :(

No, you cannot. You can decrease the workers of SOGo to something along 3-4. Deleting the SA rules file data/conf/rspamd/local.d/spamassassin.conf and restarting rspamd-mailcow does help, too. It does not help filtering, but it helps with resources.
1 GB will not work reliable anyway, sorry.

[MAGICCC]

40GB SSD is enough space, but 1GB of RAM is pretty low. We recommend to have atleast 3, better 4GB of RAM.
https://mailcow.github.io/mailcow-dockerized-docs/prerequisite-system/#minimum-system-resources

[akash07k]

Oh, ok. even though I disable clamav, then too it is not going to work properly on 1gb ram?

[akash07k]

If no, then can you please suggest me any light opensource mail server? :(

[mkuron]

Any solution that provides functionality similar to Mailcow‘s SOGo and has a modern spam filter like rspamd will end up very close to that 1 GB limit. You can actually get Mailcow below 1 GB RAM if you disable ClamAV and tweak rspamd and SOGo a bit, but you still need memory for the operating system. So for all aims and purposes, 2 GB is going to be the minimum for Mailcow and probably any modern fully-featured groupware solution.

If you need to fit into 1 GB of RAM (effectively ~800 MB accounting for kernel and background services), your best bet is to just run a bare Postfix and Dovecot (which might consume 100-200 MB each). You‘ll also want to have a few hundred MB of free space that the kernel can use as cache etc. and you don‘t want to max out your RAM because things tend to get quite sluggish when the kernel starts swapping to disk once you are out of RAM.

[Adorfer]

Please make some kind of FAQ section in the doc about RAM&CPU footprint of MTAs with effective antispam. (i run frequently into discussions "why mailcow is a RAM-hogger", explaining the above over and over again.)

[andryyy]

That's a good idea.