Mailcow-dockerized: Disable SGO

[kr19dev]

Mail-Cows SGO is great. But what if you like to use different software for caldav and carddav. Is there a way to disable sgo before spawn the container the first tine? An option in mailcow.cfg?

[MAGICCC]

No there's no option to disable SOGo yet. You can either stop the container (but please let it start after an update first) or you can decrease the workercount to 1 for example to let it run with min. RAM usage

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[PSandro]

Is there any update on this? As #3345 shows, there is demand on this option to disable SOGo completely.
As a workaround: How do I properly let mailcow stop SOGo _automatically_ after it started? :thinking:

[andryyy]

You can create a proper pull request if you need this option. :)

[whalehub]

@kr19dev @PSandro It looks like this feature was recently added in this commit: https://github.com/mailcow/mailcow-dockerized/commit/200167458e4025e4fc5d4317382760ffa9fb05a3#diff-bd6af8ddc3fbe4d221556680bc00048f

After changing SKIP_SOGO=n to SKIP_SOGO=y in my mailcow.conf file and restarting Mailcow, SOGo is gone from the list of apps and its container only consumes 2MB of RAM.