[GH-ISSUE #769] Flag a message as read on open not working #469

New issue

Closed

opened 2026-02-25 21:35:06 +03:00 by kerem · 4 comments

kerem commented

2026-02-25 21:35:06 +03:00

Owner

Originally created by @tianze0926 on GitHub (Sep 18, 2023).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/769

Originally assigned to: @IrAlfred on GitHub.

💬 Question

I set up cypht using docker with the example docker-compose, and added a custom IMAP server.

After I open an unread message, the message would still be shown as unread. However it would work as expected if I explicitly select the message and press the Read button.

I examined the Don't flag a message as read on open option and it's not toggled.

What am I missing here?

Originally created by @tianze0926 on GitHub (Sep 18, 2023). Original GitHub issue: https://github.com/cypht-org/cypht/issues/769 Originally assigned to: @IrAlfred on GitHub. ## 💬 Question I set up cypht using docker with the example docker-compose, and added a custom IMAP server. After I open an unread message, the message would still be shown as unread. However it would work as expected if I explicitly select the message and press the `Read` button. I examined the `Don't flag a message as read on open` option and it's not toggled. What am I missing here?

kerem closed this issue

2026-02-25 21:35:06 +03:00

kerem commented

2026-02-25 21:35:07 +03:00

Author

Owner

@metorm commented on GitHub (Mar 26, 2024):

I got this too. Is there a minimal timeout or something similar?

@metorm commented on GitHub (Mar 26, 2024): I got this too. Is there a minimal timeout or something similar?

kerem commented

2026-02-25 21:35:07 +03:00

Author

Owner

@marclaporte commented on GitHub (Sep 1, 2025):

@tianze0926 @metorm @IrAlfred This is pretty old.

Can someone retest in latest 2.4.x and master?

The monthly Cypht community meetings are a great opportunity to show bugs: https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings

@marclaporte commented on GitHub (Sep 1, 2025): @tianze0926 @metorm @IrAlfred This is pretty old. Can someone retest in latest 2.4.x and master? The monthly Cypht community meetings are a great opportunity to show bugs: https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings

kerem commented

2026-02-25 21:35:07 +03:00

Author

Owner

@IrAlfred commented on GitHub (Sep 1, 2025):

@tianze0926 @metorm @IrAlfred This is pretty old.

Can someone retest in latest 2.4.x and master?

The monthly Cypht community meetings are a great opportunity to show bugs: https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings

Yes, I will retest it

@IrAlfred commented on GitHub (Sep 1, 2025): > [@tianze0926](https://github.com/tianze0926) [@metorm](https://github.com/metorm) [@IrAlfred](https://github.com/IrAlfred) This is pretty old. > > Can someone retest in latest 2.4.x and master? > > The monthly Cypht community meetings are a great opportunity to show bugs: https://github.com/cypht-org/cypht/wiki/Monthly-Community-Meetings Yes, I will retest it

kerem commented

2026-02-25 21:35:07 +03:00

Author

Owner

@IrAlfred commented on GitHub (Sep 24, 2025):

Hi @tianze0926 ,

I've invested time in trying to reproduce the behavior you described.

I tested multiple versions of the Cypht Docker image (v2.3.0, 2.4.0, and 2.4.2) using the example docker-compose setup with a custom IMAP server. In all my tests, opening an unread message correctly marked it as read.

Since I cannot reproduce the issue with the current versions, it appears the problem may have already been fixed. I am closing this ticket for now.

Please feel free to reopen this issue if you encounter the problem again and it would be helpful if you could specify your exact Docker image tag.

@IrAlfred commented on GitHub (Sep 24, 2025): Hi @tianze0926 , I've invested time in trying to reproduce the behavior you described. I tested multiple versions of the Cypht Docker image (v2.3.0, 2.4.0, and 2.4.2) using the example docker-compose setup with a custom IMAP server. In all my tests, opening an unread message correctly marked it as read. Since I cannot reproduce the issue with the current versions, it appears the problem may have already been fixed. I am closing this ticket for now. Please feel free to reopen this issue if you encounter the problem again and it would be helpful if you could specify your exact Docker image tag.