[{"_1":2,"_169":-5,"_170":-5},"loaderData",{"_3":4,"_18":19,"_25":26,"_147":148},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16,"_17":11},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","dockerRebrandTour","routes/_layout",{"_20":-5,"_21":22,"_23":11,"_24":22},"username","isAskGordonEnabled",true,"showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_93":-5,"_94":95,"_134":-5,"_135":11,"_136":22,"_137":11,"_138":11,"_139":11,"_140":-5,"_141":11,"_142":-5,"_143":144,"_145":96,"_146":-7},"canonicalUrl","https://chstno1.isgood.host/r/pmietlicki/sogo-from-sources/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","pmietlicki","reponame","sogo-from-sources","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_47":48,"_50":51,"_52":53,"_54":11,"_55":56,"_57":58,"_59":60,"_43":35,"_32":33,"_62":63,"_64":49,"_65":66,"_67":68,"_69":70,"_71":-5,"_72":73,"_74":75,"_76":11,"_77":33,"_78":79,"_84":11,"_85":86,"_90":33,"_91":92},"categories",[42],{"_43":44,"_45":46},"name","Web servers","slug","web-servers","content_types",[49],"image","date_registered","2021-02-24T17:14:31.63777Z","description","A working docker image for sogo directly build from official stable release sources with activesync","is_private","last_updated","2026-05-05T00:10:46.750642Z","last_modified","2026-05-05T00:10:54.591976Z","media_types",[61],"application/vnd.docker.container.image.v1+json","pull_count",48849,"repository_type","star_count",2,"status",1,"status_description","active","source","collaborator_count",0,"full_description","# SOGo for Docker\n\n[SOGo](http://www.sogo.nu) is a fully supported and trusted groupware server with a focus on scalability and open standards. SOGo is released under the GNU GPL/LGPL v2 and above. \n\nThis Dockerfile packages SOGo as packaged by ubuntu, together with Apache 2 and memcached.\n\n## Setup\n\nThe image stores configuration, logs and backups in `/srv`, which you should persist somewhere. Example configuration is copied during each startup of the container, which you can adjust for your own use. For creating the initial directory hierarchy and example configuration, simply run the container with the `/srv` volume already exposed or linked, for example using\n\n docker run -v /srv/sogo:/srv pmietlicki/sogo\n\nAs soon as the files are created, stop the image again. You will now find following files:\n\n .\n ├── etc\n │ ├── apache-SOGo.conf.orig\n │ └── sogo.conf.orig\n └── lib\n └── sogo\n └── GNUstep\n ├── Defaults\n └── Library\n\nCreate copies of the configuration files named `apache-SOGo.conf` and `sogo.conf.orig`. Don't change or link the `.orig` files, as they will be overwritten each time the container is started. They can also be used to see differences on your configuration after SOGo upgrades.\n\n### Database\n\nA separate database is required, for example a PostgreSQL container as provided by the Docker image [`postgres`](https://chstno1.isgood.host/_/postgres), but also any other database management system SOGo supports can be used. Follow the _Database Configuration_ chapter of the SOGo documentation on these steps, and modify the sogo.conf` file accordingly. The following documentation will expect the database to be available with the SOGo default credentials given by the official documentation, adjust them as needed. If you link a database container, remember that it will be automatically added to the hosts file and be available under the chosen name.\n\nFor a container named `sogo-postgresql` linked as `db` using `--link=\"sogo-postgresql:db\"` with default credentials, you would use following lines in the `sogo.conf`:\n\n SOGoProfileURL = \"postgresql://sogo:sogo@db:5432/sogo/sogo_user_profile\";\n OCSFolderInfoURL = \"postgresql://sogo:sogo@db:5432/sogo/sogo_folder_info\";\n OCSSessionsFolderURL = \"postgresql://sogo:sogo@db:5432/sogo/sogo_sessions_folder\";\n\nSOGo performs schema initialziation lazily on startup, thus no database initialization scripts must be run.\n\n### memcached\n\nAs most users will not want to separate memcached, there is a built-in daemon. It can be controled by setting the environment variable `memcached`. If set to `false`, the built-in memcached will not start, make sure to configure an external one. Otherwise, the variable holds the amount of memory dedicated to memcached in MiB. If unset, a default of 64MiB will be used.\n\n### Sending Mail\n\n SOGoMailingMechanism = \"smtp\";\n SOGoSMTPServer = \"yoursmtpserver.localdomain.local\";\n \nFor further details in MTA configuration including SMTP auth, refer to SOGo's documentation.\n\n### Apache and HTTPs\n\nAs already given above, the default Apache configuration is already available under `etc/apache-SOGo.conf.orig`. The container exposes HTTP (80), HTTPS (443) and 8800, which is used by Apple devices, and 20000, the default port the SOGo daemon listens on. You can either directly include the certificates within the container, or use an external proxy for this. Make sure to only map the required ports to not unnecessarily expose daemons.\n\nYou need to adjust the `` section and include port, server name and url to match your setup.\n\n \n ## adjust the following to your configuration\n RequestHeader set \"x-webobjects-server-port\" \"80\"\n RequestHeader set \"x-webobjects-server-name\" \"%{HTTP_HOST}e\" env=HTTP_HOST\n RequestHeader set \"x-webobjects-server-url\" \"http://%{HTTP_HOST}e\" env=HTTP_HOST\n\nIf you want to support iOS-devices, add appropriate `.well-known`-rewrites in either the Apache configuration or an external proxy.\n\nFor ActiveSync support, additionally add/uncomment the following lines:\n\n ProxyPass /Microsoft-Server-ActiveSync \\\n http://127.0.0.1:20000/SOGo/Microsoft-Server-ActiveSync \\\n retry=60 connectiontimeout=5 timeout=360\n\n\n### Cron-Jobs: Backup, Session Timeout, Sieve\n\nSOGo heavily relies on cron jobs for different purposes. The image provides SOGo's original cron file as `./etc/cron.orig`. Copy and edit it as `./etc/cron`. The backup script is available and made executable at the predefined location `/usr/share/doc/sogo/sogo-backup.sh`, so backup is fully functional immediately after uncommenting the respective cron job.\n\n### Further Configuration\n\nUnlike the Debian and probably other SOGo packages, the number of worker processes is not set in `/etc/default/sogo`, but the normal `sogo.conf`. Remember to start a reasonable number of worker processes matching to your needs (8 will not be enough for medium and larger instances):\n\n WOWorkersCount = 8;\n\nActiveSync requires one worker per concurrent connection.\n\nAll other configuration options have no special considerations.\n\n## Running a Container\n\nRun the image in a container, expose ports as needed and making `/srv` permanent. An example run command, which links to a database container named `db` and uses an external HTTP proxy for wrapping in HTTPS might be\n\n docker run -d \\\n --name='sogo' \\\n --publish='127.0.0.1:80:80' \\\n --link='sogo-postgresql:db' \\\n --volume='/srv/sogo:/srv' \\\n pmietlicki/sogo\n\n## Upgrading and Maintenance\n\nMost of the time, no special action must be performed for upgrading SOGo. Read the _Upgrading_ section of the [Installation Manual](http://www.sogo.nu/files/docs/SOGo%20Installation%20Guide.pdf) prior upgrading the container to verify whether anything special needs to be considered.\n\nAs the image builds on [`phusion/baseimage`](https://github.com/phusion/baseimage-docker), you can get a shell for running update scripts when necessary or perform similar maintenance operations by adding `/sbin/my_init -- /bin/bash` as run command and subsequently attaching to the container:\n\n docker run -t -i -d \\\n --name='sogo' \\\n --publish='127.0.0.1:80:80' \\\n --link='sogo-postgresql:db' \\\n --volume='/srv/sogo:/srv' \\\n pmietlicki/sogo /sbin/my_init -- /bin/bash\n\nThis is fine for running update scripts on the database. To be able to perform persistent changes to the file system (without creating new containers), red the [`phusion/baseimage`](https://github.com/phusion/baseimage-docker) documentation on attaching to the container.\n\n## Rancher usage example\n\nI created a stolon external database under stolon-proxy.pg12, then created a new user and database named \"sogo\" under pgadmin4.\n\n### Variables\nYou can set http_proxy, https_proxy and no_proxy if you are behind a corporate proxy for example.\n\n### Health and liveness check \nFor Health Check, you can check \"HTTP request returns a successful status (2xx or 3xx)\" with a request path to \"/SOGo\" on port 80\n\n### Volumes\nI put all the configuration with Config Map named sogo and Config Map values (sogo.conf and apache-SOGo.conf, optionnaly cron, **it is case sensitive**).\nThen for the volumes, I used :\n\n#### Sogo Config Files\n\n* Volume Name : sogo-conf\n* Default Mode : 644\n* Config Map Name : sogo with Items : All keys\n* Mount Point : /srv/etc/\n\n#### Cron (if needed)\n\n* Volume Name : sogo-nfs\n* Persisent Volume Claim : sogo-nfs (a new persistent volume claim with nfs as default provider with Many Nodes Read-Write)\n* Mount Point : /srv\n\n### Configuration exemple\n\n#### apache-SOGo.conf\n\n Alias /SOGo.woa/WebServerResources/ \\\n /usr/lib/GNUstep/SOGo/WebServerResources/\n Alias /SOGo/WebServerResources/ \\\n /usr/lib/GNUstep/SOGo/WebServerResources/\n \n AllowOverride None\n \n Order deny,allow\n Allow from all\n \n = 2.4>\n Require all granted\n \n \n ExpiresActive On\n ExpiresDefault \"access plus 1 year\"\n \n \n ProxyRequests Off\n SetEnv proxy-nokeepalive 1\n ProxyPreserveHost On\n #Example for redirect from / to /SOGo\n RedirectMatch ^/$ http://webmail.localdomain.local/SOGo\n ProxyPass /SOGo http://127.0.0.1:20000/SOGo retry=0\n \n \n RequestHeader set \"x-webobjects-server-port\" \"80\"\n RequestHeader set \"x-webobjects-server-name\" \"%{HTTP_HOST}e\" env=HTTP_HOST\n RequestHeader set \"x-webobjects-server-url\" \"http://%{HTTP_HOST}e\" env=HTTP_HOST\n ## When using proxy-side autentication, you need to uncomment and\n ## adjust the following line:\n RequestHeader unset \"x-webobjects-remote-user\"\n #RequestHeader set \"x-webobjects-remote-user\" \"%{REMOTE_USER}e\" env=REMOTE_USER\n RequestHeader set \"x-webobjects-server-protocol\" \"HTTP/1.0\"\n \n AddDefaultCharset UTF-8\n Order allow,deny\n Allow from all\n \n #For Apple autoconfiguration\n \n RewriteEngine On\n RewriteRule ^/.well-known/caldav/?$ /SOGo/dav [R=301]\n RewriteRule ^/.well-known/carddav/?$ /SOGo/dav [R=301]\n \n\n#### sogo.conf\n {\n SOGoProfileURL = \"postgresql://sogo:sogo@stolon-proxy.pg12:5432/sogo/sogo_user_profile\";\n OCSFolderInfoURL = \"postgresql://sogo:sogo@stolon-proxy.pg12:5432/sogo/sogo_folder_info\";\n OCSSessionsFolderURL = \"postgresql://sogo:sogo@stolon-proxy.pg12:5432/sogo/sogo_sessions_folder\";\n OCSEMailAlarmsFolderURL = \"postgresql://sogo:sogo@stolon-proxy.pg12:5432/sogo/sogo_alarms_folder\";\n SOGoLanguage = English;\n SOGoPageTitle = \"Webmail\";\n SOGoAppointmentSendEMailNotifications = YES;\n SOGoMailingMechanism = smtp;\n SOGoSMTPServer = smtp-server.localdomain.local;\n SOGoTimeZone = UTC;\n SOGoSentFolderName = Sent;\n SOGoTrashFolderName = Trash;\n SOGoDraftsFolderName = Drafts;\n SOGoIMAPServer = \"imaps://imap-server.localdomain.local:143/?tls=YES&tlsVerifyMode=none\";\n SOGoIMAPAclConformsToIMAPExt = YES;\n SOGoVacationEnabled = NO;\n SOGoForwardEnabled = NO;\n SOGoSieveScriptsEnabled = NO;\n SOGoFirstDayOfWeek = 0;\n SOGoMailMessageCheck = manually;\n SOGoMailAuxiliaryUserAccountsEnabled = NO;\n SOGoMemcachedHost = 127.0.0.1;\n WOWorkersCount = 8;\n /* LDAP authentication example */\n SOGoUserSources = (\n {\n type = ldap;\n CNFieldName = cn;\n UIDFieldName = uid;\n IDFieldName = uid; // first field of the DN for direct binds\n bindFields = (mail, uid); // array of fields to use for indirect binds\n baseDN = \"ou=mycompany,o=localdomain,c=local\";\n bindDN = \"cn=Directory Manager\";\n bindPassword = \"mypassword\";\n canAuthenticate = YES;\n displayName = \"Company Address Book\";\n hostname = ldap://ldap.localdomain.local:389;\n id = public;\n isAddressBook = YES;\n }\n );\n }\n\n#### cron (if needed)\n # Sogod cronjobs\n # Vacation messages expiration\n # The credentials file should contain the sieve admin credentials (username:passwd)\n #0 0 * * * sogo /usr/sbin/sogo-tool update-autoreply -p /etc/sogo/sieve.creds\n # Session cleanup - runs every minute\n # - Ajust the nbMinutes parameter to suit your needs\n # Example: Sessions without activity since 60 minutes will be dropped:\n #* * * * * sogo /usr/sbin/sogo-tool expire-sessions 60 > /dev/null 2>&1\n # Email alarms - runs every minutes\n # If you need to use SMTP AUTH for outgoing mails, specify credentials to use\n # with '-p /path/to/credentialsFile' (same format as the sieve credentials)\n #* * * * * sogo /usr/sbin/sogo-ealarms-notify > /dev/null 2>&1\n # Daily backups\n # - writes backups to /var/backups/sogo/\n # - will keep 31 days worth of backups by default\n # - runs once a day by default, but can run more frequently\n #30 0 * * * sogo /usr/sbin/sogo-backup\n\n#### Config for an external dovecot imap proxy for exchange (owa), you can use official dovecot docker image\n mail_uid = 1000\n mail_gid = 1000\n protocols = imap imaps\n listen = *\n mail_location = imapc:~/imapc\n imapc_host = owa.localdomain.domain\n imapc_port = 993\n imapc_ssl = imaps\n imapc_ssl_verify = no\n passdb {\n driver = imap\n args = host=owa.localdomain.domain ssl=imaps port=993 ssl_ca_file=/certs/cert_chain.cer\n default_fields = userdb_imapc_user=%u userdb_imapc_password=%w\n }\n userdb {\n driver = prefetch\n }\n mail_home = /srv/mail/%u\n auth_mechanisms = plain login\n verbose_ssl = yes\n ssl = yes\n ssl_cert =

pmietlicki/sogo-from-sources

Tags for pmietlicki/sogo-from-sources