Ckruijntjens reinstallation is my thought. I am only in the testing phase right now. Trying to get something in place to replace all my legacy G-Suite accounts I have since the writing is on the wall for the demise of the “free” ones.
EnglishUnable to login to SOGo
kameleon normally a basic install would cover all. Everything should work.
- Edited
Usually I know it is a good idea to change defaults, but this may have been my problem. After I generate the config, should I change:
DBNAME=mailcow
DBUSER=mailcow
DBPASS and DBROOT were generated properly with long complex values.
kameleon no you don’t have to change this
a year later
Having the same issue. Upon checking the log seeing this.
mailcowdockerized-sogo-mailcow-1 | May 6 12:50:24 e0890c8d475b sogod [84]: SOGoRootPage Login from 'XX.YY.ZZ.AB' for user 'user@example.tld' might not have worked - password policy: 65535 grace: -1 expire: -1 bound: 0
mailcowdockerized-sogo-mailcow-1 | May 6 12:50:24 e0890c8d475b sogod [84]: XX.YY.ZZ.AB "POST /SOGo/connect HTTP/1.0" 403 33/91 0.020 - - 3M - 12
mailcowdockerized-sogo-mailcow-1 | May 6 12:50:27 e0890c8d475b sogod [84]: XX.YY.ZZ.AB "GET /SOGo/so/ HTTP/1.0" 200 9503/0 0.013 39166 75% 1M - 12
mailcowdockerized-sogo-mailcow-1 | May 6 12:50:27 e0890c8d475b sogod [84]: XX.YY.ZZ.AB "POST /SOGo/so/passwordRecoveryEnabled HTTP/1.0" 403 0/49 0.001 - - 0 - 12User were created from UI and tried to reset password multiple times and having same issue.
I have the same issue on a new docker install.
Came to this forum to see if I could find the answer.
I am looking to replace a iRedmail server I am running now.
This install is going to run on Arch Linux.
I changed the users password and sogo let me login.
I must not have entered the correct password.
I changed multiple times and not working
The other thing I did was use the entire email address as the username
I did new install and create same user and password and it didn’t work, but when I reboot new system it worked. But old system still having same.
2 months later
Hi. I need that only HR can send an e-mail to the group mail in the following ways.
Only hr@domain.com can send an e-mail to groups@domain.com but others can not send an e-mail to groups@domain.com.
Is there any way to accomplish this problem?
Anyway, guys… SOGo can, of course, be ignored…
By using STMP, POP3, things done… Thanks god.. mailcow
⋊> /o/mailcow-dockerized on master ⨯ sudo docker-compose up -d 08:33:10
[sudo] password for jiapei:
[+] Running 19/19
Container mailcowdockerized-solr-mailcow-1 Running 0.0s
Container mailcowdockerized-memcached-mailcow-1 Running 0.0s
Container mailcowdockerized-redis-mailcow-1 Running 0.0s
Container mailcowdockerized-dockerapi-mailcow-1 Running 0.0s
Container mailcowdockerized-unbound-mailcow-1 Running 0.0s
Container mailcowdockerized-clamd-mailcow-1 Running 0.0s
Container mailcowdockerized-mysql-mailcow-1 Running 0.0s
Container mailcowdockerized-php-fpm-mailcow-1 Running 0.0s
Container mailcowdockerized-watchdog-mailcow-1 Started 3.1s
Container mailcowdockerized-dovecot-mailcow-1 Running 0.0s
Container mailcowdockerized-rspamd-mailcow-1 Running 0.0s
Container mailcowdockerized-postfix-mailcow-1 Running 0.0s
Container mailcowdockerized-olefy-mailcow-1 Running 0.0s
Container mailcowdockerized-sogo-mailcow-1 Running 0.0s
Container mailcowdockerized-netfilter-mailcow-1 Running 0.0s
Container mailcowdockerized-ofelia-mailcow-1 Running 0.0s
Container mailcowdockerized-nginx-mailcow-1 Started 3.1s
Container mailcowdockerized-acme-mailcow-1 Started 2.5s
Container mailcowdockerized-ipv6nat-mailcow-1 Started Clearly, sogo is running.
Does SOGo Login needs some extra activation? But NOT activated by default ?
If so, how?
Thank you very much…
Pei
- Edited
But NOT activated by default ?
I guess you played around with the mailbox template. It is by default activated. Please check your mailbox configurations.
@esackbauer
Thank you for your reply…
But Nope… It NOT mailbox template. Anyway, so far, I cannot loging SOGo, even with default username admin and default password moohoo ….
That’s fine though…
Have a nice weekend…
6 months later
Interesting to find this discussion here, maybe this will get some cases solved in the future.
In order to create smaller container names, I shortened the following in mailcow.conf:
COMPOSE_PROJECT_NAME=mailcowdockerized
I shortened it to COMPOSE_PROJECT_NAME=mc
Result: unable to login.
Steps to reproduce:
docker compose down
change the value in mailcow,conf
docker compose up -d
No more authentication possible…
After resetting in the same order, all worked again…
roelofz Result: unable to login.
Which user you tried to login with?
Admin login to SOGo is disabled by default (for a good reason):
Admin login to SOGo - mailcow: dockerized documentation docs.mailcow.email
2 months later
I had the same problem with all user accounts on the server, couldn’t log in to sogo. But i just:
docker restart mailcowdockerized-sogo-mailcow-1
Now sogo is working normally 
No one is typing