Bug 49449 - Cron running in Horde container triggers server password change
Cron running in Horde container triggers server password change
Status: RESOLVED DUPLICATE of bug 49587
Product: UCS
Classification: Unclassified
Component: Mail - Horde
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Mail maintainers
Mail maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-05-10 18:26 CEST by Kevin
Modified: 2019-10-15 10:15 CEST (History)
7 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 4: A User would return the product
User Pain: 0.229
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin 2019-05-10 18:26:41 CEST
+++ This bug was initially created as a clone of Bug #48486 +++

As described in this forum post:
https://help.univention.com/t/horde-container-machine-password-mismatch-in-configuration-users-cannot-login/10944

Still seeing this problem. Occasionally users will complain that they cannot log in to webmail. If I go into the settings and simply apply without making any changes it works again.
Comment 1 Felix Botner univentionstaff 2019-05-13 09:32:44 CEST
This should be fixed with the latest horde App - 5.2.17-3 (a server password hook for horde has been added).
Comment 2 Kevin 2019-05-13 13:35:35 CEST
Yes, I thought it would be fixed, but it's still happening as far as I can tell. There were other uses in the forum thread who see the problem with the updated version as well. That's all I know right now. Not sure what I should look for to track it down when it happens again.
Comment 3 Kevin 2019-07-15 05:33:51 CEST
Can someone please explain why this was closed as resolved invalid?

In the linked thread from the original comment it explains that the problem is still occurring in the version that was supposed to be the fix.

That thread also stated not to add comments to the existing bug, but to clone it instead. 

That's what I did, but it doesn't seem like anyone has looked at this again.

I'd just like to understand what if anything should have been done differently in this case to have the bug looked at again. TIA
Comment 4 Felix Botner univentionstaff 2019-10-15 10:15:52 CEST
This is fixed with Bug #49587

*** This bug has been marked as a duplicate of bug 49587 ***