Mails marked as read displayed as unread after a while causing a lot of output in logs
-
Good morning,
as i wrote yesterday in another post some of my users have mails which you can mark as read but after a while, not later than the next morning, they are back as unread.
A workaround is to move the messages in another folder. There they stay unread. After that you can move them back to the inbox an they stay unread.
BUT: Even if you get them marked as unread the main problem with the mails persists. For every mail there is a log entry.
This issue occured in core version 8.6.81.475. I am not sure if new emails are still affected, but i have to correct this problem without deleting the mails.
-
Hi,
imo refers to kopano-server[]: setSyncStatus(): collision (end of thread)
An update to (community-build) core 8.7.80.27 should fix this.++umgfoin.
-
Hi,
thanks for answering. I read this post and updated to 8.7.80.27-22.1 and the problem is still there.
I am using SLES12 SP3 and maybe that is the problem. There are still a few unresolved dependencies, especially with python3 packages.
I am not sure if the unresolved dependencies can be resolved for SLES12. The python3-bsddb3 package is not supported by SLES12, but it is supported by SLES15. -
@sturzhelmut said:
especially with python3 packages.
can’t imagine, the above is kc-server functionality.
Kopano-server has/was restarted since upgrading?Can @deHoeninger confirm that community-build 8.7.80.27 includes libserver: Fix AddChange INSERT instead of REPLACE?
I’m building from master which is usually a couple of commits ahead of community-builds.Can you set the server log-level to debug and post a wider context of the key-violation?
++umgfoin.
-
@umgfoin said in Mails marked as read displayed as unread after a while causing a lot of output in logs:
Can @deHoeninger confirm that community-build 8.7.80.27 includes libserver: Fix AddChange INSERT instead of REPLACE?
Hi all,
I’ve installed latest nightly and still have the mentioned errors in the logs. So I guess, the relevant changes to master don’t found the way into latest nightly yet. I’m currently waiting for next version.Best Jan
-
@deHoeninger, @umgfoin
Thank you for replying. With my ordered subscription the issue should be away.
