- Edited
How do I disable SOGo completely?
Is docker-compose stop sogo-mailcow
enough?
Do I have to disable it in the mailcow.conf too?
English
How do I disable SOGo completely?
Is docker-compose stop sogo-mailcow
enough?
Do I have to disable it in the mailcow.conf too?
Disable it in mailcow.conf, then the container will start but just idle
Have something to say?
Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!
MAGIC Once I’ve changed the config, do I have to restart the mailcow
container?
Set SKIP_SOGO=y
. Then
docker compose stop
docker compose start
and SOGo container is still running, and SOGo itself is.
Do a down and an up -d
I have trouble disabling SOGo. I have set in mailcow.conf:
SKIP_SOGO=y
SKIP_SOLR=y
I’m doing docker compose down and up -d. I can see that sogo and solr are starting:
root@ile2:/opt/mailcow-dockerized# docker compose up -d
[+] Running 20/20
Network mailcowdockerized_mailcow-network Created 0.1s
Container mailcowdockerized-unbound-mailcow-1 Started 1.1s
Container mailcowdockerized-sogo-mailcow-1 Started 1.7s
Container mailcowdockerized-dockerapi-mailcow-1 Started 1.2s
Container mailcowdockerized-memcached-mailcow-1 Started 1.0s
Container mailcowdockerized-olefy-mailcow-1 Started 1.4s
Container mailcowdockerized-watchdog-mailcow-1 Started 1.6s
Container mailcowdockerized-solr-mailcow-1 Started 1.3s
Container mailcowdockerized-redis-mailcow-1 Started 1.6s
Container mailcowdockerized-php-fpm-mailcow-1 Started 2.0s
Container mailcowdockerized-mysql-mailcow-1 Started 1.6s
Container mailcowdockerized-clamd-mailcow-1 Started 1.7s
Container mailcowdockerized-nginx-mailcow-1 Started 2.5s
Container mailcowdockerized-postfix-mailcow-1 Started 2.2s
Container mailcowdockerized-dovecot-mailcow-1 Started 2.4s
Container mailcowdockerized-acme-mailcow-1 Started 3.2s
Container mailcowdockerized-netfilter-mailcow-1 Started 2.5s
Container mailcowdockerized-rspamd-mailcow-1 Started 3.1s
Container mailcowdockerized-ofelia-mailcow-1 Started 3.0s
Container mailcowdockerized-ipv6nat-mailcow-1 Started 3.2s
In the dashboard/debug screen I see that solr may not be running but sogo is (?)
So … I’m not sure how to disable sogo (and solr?).
I did this, but dashboard is still showing that sogo running. The container definitely isn’t running anymore, but dashboard is saying that it is.
root@ile2:/opt/mailcow-dockerized# docker stop mailcowdockerized-sogo-mailcow-1
mailcowdockerized-sogo-mailcow-1
root@ile2:/opt/mailcow-dockerized# docker stop mailcowdockerized-solr-mailcow-1
mailcowdockerized-solr-mailcow-1
root@ile2:/opt/mailcow-dockerized#
First of all don’t fiddle around with the compose file. because that can have unwanted side-effects. The containers must always be started together with the rest of the stack.
You can stop them manually afterwards, as you did, but this is not really necessary, because when they are disabled in the mailcow.conf the number of processes they can use are limited, meaning they are running basically in an idle state. So you won’t gain anything regarding memory consumption by stopping them.
I don’t know why one is shown as stopped in the UI and the other one isn’t, even though both are running and doing nothing. However, I can tell you that it behaves exactly the same on my instance, and that this is only a cosmetic issue.
Good thing you warned, I was about to go fiddle with the compose file next.
I’m mainly concerned that there isn’t any extra features available (sogo), so if it’s disabled, then it should be ok.
If i installed roundcube as third-party, and i want to disable SoGo, i will be able to use roundcube instead of SoGo ? and will run as expected , same like SoGo, being able to send and receive mails from roundcube, if i add mailboxes from mailcow admin interface?
Xerud Yes its possible: