When setting the value of force_pw_update=1 in the create inbox API

{
“local_part”: “{{local_part}}”,
“domain”: “{{domain}}”,
“name”: “{{name}}”,
“password”: “{{password}}”,
“password2”: “{{password2}}”,
“active”: {{active}},
“force_pw_update”: {{force_password_update}}
}

[unknown]
Also encountering the error when creating the mailbox in mailcow admin panel.

[unknown]
Also encountering the error when creating the mailbox in mailcow admin panel.

[unknown]
Also encountering the error when creating the mailbox in mailcow admin panel.

You are right, it’s the same problem on my mailcow. Never tested this function before though…

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!

Yes, that seems to be a bug, I’m currently debugging a little bit. Upon setting the force password reset option the password hash in the database view “sogo_view” changes to another value, and that’s the reason why you can’t login anymore. It’s switched back to the original hash after removing the checkbox again.

EDIT: It’s really strange as it seems to be intended: mailcow/mailcow-dockerizedblob/master/data/Dockerfiles/sogo/bootstrap-sogo.sh#L38

If the password change option is set (force_pw_update) then a static SSHA256 hash is set for the user so that he can’t login in SoGo.
BUT he can login into the mailcow UI and has to change his password there. I guess that’s because SoGo itself doesn’t have a password change function?

EDIT 2: just had a look, there is no option in SoGo to change your password through the SoGo UI, so that’s the reason. The user has to change the password via the mailcow UI

    6 days later

    chulim ah OK, but it still wouldn’t work due to the fixed SSHA256 hash which is set by mailcow…

      No one is typing