All the crypto on SOGo are based on the openssl lib. Maybe it is missing from the frederickzh image.
Cheers, -- Quentin Hivert Lead Dev R&D [email protected] Alinto 19, quai Perrache FR-69002 Lyon https://www.alinto.com Linkedin FR Le Lundi, Juin 15, 2026 19:19 CEST, "556loop" ([email protected]) <[email protected]> a écrit: I try the scenario in a VM with Debian 12. This works. I will change my strategy from docker to VM. The container frederickzh/archlinux-sogo:latest is on Arch Linux. Perhaps this is the problem. 556loop <[email protected]> schrieb am Sonntag, 14. Juni 2026 um 14:00: Hi, I'm using a docker container for SOGo (frederickzh/archlinux-sogo:latest) and postgres:18.4 as database backend. I want to use the authentification via SQL and use this part in my sogo.conf SOGoUserSources = ( { type = sql; id = directory; viewURL = "postgresql://sogo:password@sogo-db:5432/sogo/sogo_users"; canAuthenticate = YES; isAddressBook = YES; userPasswordAlgorithm = md5; } ); The password for database is calculate with "echo -n 'password' | md5sum". This is the entry in my postgresql database table sogo_users: c_uid c_name c_password c_cn mailuser user 5f4dcc3b5aa765d61d8327deb882cf99 user [email protected] I get the this error after failed login:sogo | Jun 13 20:43:18 sogod [97]: SOGoRootPage Login from '192.168.20.5' for user 'user' might not have worked - p assword policy: 65535 grace: -1 expire: -1 bound: 0 If I set "userPasswordAlgorithm = plain" it works after I update my sogo_users table with "password". What is the reason that only plain works? sha256 or sha512 also not working. Thanks for help ... :-) Bye, Damgis
