What follows is a problem description for version 3.1.5. After updating to 3.2.1, the issue seems to be resolved only *partly*. At the end of the mail, you can find a problem description for version 3.2.1.
When selecting a message in the Mail module, the message is displayed in the preview pane on the right side but it is not marked as read. In the top right an error message says: Request failed Looking at the log file of sogod I see error messages such as the following each time I select a message: Nov 17 12:28:35 sogod [54352]: 80.128.92.18, 80.128.92.18, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/2239792221/markMessageRead HTTP/1.1" 500 286/0 0.875 - - - Apparently, it's an HTTP 500 error (Apache24 says the same in its log file). I don't know how to debug this further. As it seems, the error occurs on my account only. I don't use the webmail interface very often, so I cannot say since when this error occurs. The following I have found out so far: $ grep markMessageRead /var/log/sogo/sogo.log | grep [email protected] Oct 07 17:43:58 sogod [69895]: 37.201.169.224, 37.201.169.224, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/6089/markMessageRead HTTP/1.1" 204 0/0 0.875 - - - Oct 09 12:02:00 sogod [88029]: 37.201.169.224, 37.201.169.224, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/6217/markMessageRead HTTP/1.1" 204 0/0 0.880 - - - Oct 09 12:02:10 sogod [88029]: 37.201.169.224, 37.201.169.224, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/6193/markMessageRead HTTP/1.1" 204 0/0 0.884 - - - Oct 15 00:55:15 sogod [45507]: 80.128.92.18, 80.128.92.18, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/6766/markMessageRead HTTP/1.1" 204 0/0 0.874 - - - Nov 04 08:41:41 sogod [67386]: 80.128.92.18, 80.128.92.18, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/9269/markMessageRead HTTP/1.1" 204 0/0 0.876 - - - Nov 17 12:27:10 sogod [54354]: 80.128.92.18, 80.128.92.18, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/2239792221/markMessageRead HTTP/1.1" 500 286/0 0.895 - - - Nov 17 12:27:23 sogod [54354]: 80.128.92.18, 80.128.92.18, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/2239792220/markMessageRead HTTP/1.1" 500 286/0 0.867 - - - Nov 17 12:27:48 sogod [54351]: 80.128.92.18, 80.128.92.18, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/2239792220/markMessageRead HTTP/1.1" 500 286/0 0.866 - - - Nov 17 12:28:35 sogod [54352]: 80.128.92.18, 80.128.92.18, 10.1.4.1 "GET /SOGo/so/[email protected]/Mail/0/folderINBOX/2239792221/markMessageRead HTTP/1.1" 500 286/0 0.875 - - - As you can see, something must have happened between November 4th and 17th that 1. caused markMessageRead to return 500 instead of 204 2. made the ID of mails jump from 9269 to 2239792221 I don't know whether these two changes/issues are interrelated. As far as I can judge from the log file other users are not affected and the IDs of their mails remain in multiples of 10^3 (instead of 10^9). (I don't know sogo's internals well, so I suspect it's something like an ID that changed here.) So, I just updated to version 3.2.1, which partly resolved the issue. What has changed since version 3.1.5 is the following: - The webmail client doesn't show an error message saying "Request failed". - After previewing the message in the pane on the right, the message is marked as read in the message list. However, when refreshing the mailbox every message that was just marked as read will be shown as unread again. - In the logs I cannot see any reference to markMessageRead. I suspect that there had been some work done on this issue between the two versions I stated above but I cannot find any reference in the bug tracking system. Do you have any recommendations on how to debug the issue further or ideas what might cause the error? Any help is very much appreciated. Niklaas -- [email protected] https://inverse.ca/sogo/lists
