If I don’t want to access SOGo or need to access the web admin interface, is there any harm in disabling their docker instances? So like stopping the following:

  • mailcow/sogo
  • nginx:mainline-alpine
  • mailcow/phpfpm

  • MAGIC

    • Forum Staff
    • volunteer
    Moolevel 48
  • Post #2

1.) It’s not an adminpanel. Users should have access to it to change some options
2.) You can ‘disable’ SOGo in the mailcow.conf - it will only spawn a lightweight container
3.) When you stop the webserver your SSL certs will break too because it needs a webserver on port 80 for validation.

Why would you install such a big system just to disable one of the main things? If you only need to send and receive mails then a simple postfix/dovecot is fine…

    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 For company reasons, their options need to be run through an admin instead of doing it themselves. But yes, since we need SSL, we’ll keep up the web related docker instances. Thanks.

      No one is typing