Okay, I found the culprit.
SOGo wants sha256.hex in sogo.conf... 🙄
Thanks for reading.
Am 11.04.25 um 09:01 schrieb Jan Kriesten ([email protected]):
Hey there!
I got the dang password policy 65535 error with a freshly installed
5.12.0 nightly (Ubuntu 24), IMAP service is cyrus imapd 3.8.2:
---8<---
2025-04-11 08:27:59.523 sogod[77444:77444]
<MySQL4Channel[0x0x558a7c801490] connection=0x0x558a7c081660> SQL:
SELECT c_password FROM users WHERE c_uid = '[email protected]';
2025-04-11 08:27:59.524 sogod[77444:77444]
<MySQL4Channel[0x0x558a7c801490] connection=0x0x558a7c081660>Â Â query
has results, entering fetch-mode.
Apr 11 08:27:59 sogod [77444]: SOGoRootPage Login from '127.0.0.1' for
user '[email protected]' might not have worked - password policy: 65535
grace: -1Â expire: -1Â bound: 0
---8<---
The (SHA-256) password seems to be fetched fine from the database, the
sogo.conf also contains
userPasswordAlgorithm = sha256;
canAuthenticate = YES;
for the SOGoUserSources.
The following logins are tested fine:
testsaslauthd -u user -r realm.net -p somePass -s imap
imtest -a [email protected]
The thing works (with md5) on another server (v3.2.10 there).
I can't see any difference except for md5/sha256, but I tried md5 on the
new server and can't login with that configured as well. So I'm stuck.
Any more ideas, any more info I can provide to narrow it down?
Thanks in advance!
--- Jan.
