Summary: | New mail automatically marked as read when Claws still in tray, when receive dialog is shown | ||
---|---|---|---|
Product: | Claws Mail (GTK 2) | Reporter: | Ian Nartowicz <mozilla> |
Component: | Plugins/Notification | Assignee: | users |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | P3 | ||
Version: | 3.9.2 | ||
Hardware: | PC | ||
OS: | Linux |
Description
Ian Nartowicz
2013-10-15 18:49:52 UTC
Re-reading this, I can see it might be a little confusing just what the bug is. To summarise, it is possible for new mail to arrive while the main window is closed, but the tray icon will show no mail. Do you have the option set to go to inbox after receiving new mail? (/Mail handling/Receiving page). On the /Display/Summaries page of the prefs, for the 'Set default selection when entering a folder', 'Selection of folder opening' set to 'First new mail'? Also on the /Display/Summaries page, do you have the 'Open message when selected' option set to 'Always'? "Go to inbox" is set. "First new email" is the first selection for "Set default selection". "Open message when selected" is set to "Always". Also, "Mark message as read" is set to "on selected", after 2 seconds. With this combination, I expect that a newly received mail message will be selected, and shortly afterwards marked read, when it arrives with the Claws main window open (although that doesn't happen if the relevant inbox is already selected), which is fine. I expect it not to happen when the main window is closed, or at least not to happen until I open the window. Which is also fine. The tricky case is when the main window is closed and the receive dialog visible, then the message still gets marked read even though I have no hope of ever having seen it. You have plenty of choices and I think you can see how your choices are the cause of the behaviour you describe. What you describe is not a bug. You are actually asking for another option. I'll close this, but feel free to open a new item as an 'enhancement'. Yes, my choice of preference settings cause a bug to happen. Bad me ;) Not a bug - it's doing exactly what the settings you chose are intended to do. |