Advertisement
Front, Kernel, Security, Distributions, Development. See your byline here on LWN.net.
| |||||||||||||
|
| |||||||||||||
The Grumpy Editor reviews Claws MailThe Grumpy Editor reviews Claws MailPosted Jun 1, 2008 20:34 UTC (Sun) by quotemstr (subscriber, #45331)In reply to: The Grumpy Editor reviews Claws Mail by cventers Parent article: The Grumpy Editor reviews Claws Mail
My biggest gripe with kmail is read-flag synchronization. I have three machines, A, B, and C. A and B run kmail, and C runs OS X's Mail.app. When A marks a message read, only C notices that's read. when B marks a message read, only C notices that it's been read. The result is that on A and B, I often end up reading the same message twice. Flushing the IMAP cache doesn't help.
(Log in to post comments)
The Grumpy Editor reviews Claws Mail Posted Jun 2, 2008 10:48 UTC (Mon) by fjorba (subscriber, #6175) [Link] I'm having the same problem between Gnus (my primary client) and a couple of Thunderbirds I'm having in auxiliary machines, all with imap. Although I cannot confirm it, I'd say that it is the Thunderbirds that ignore the read flags from Gnus, or Gnus is not diligent enough to send them promptly to the imap server. It is really annoying, but I don't have the time to isolate who's fault is it. Anybody else has more details? Ferran
The Grumpy Editor reviews Claws Mail Posted Jun 2, 2008 18:37 UTC (Mon) by nix (subscriber, #2304) [Link] If 'gnus-verbose' is at least 7, you'll see messages of the form "nnimap: Setting marks in %s..." when the read flags are being updated. It's saved by 'gnus-summary-save-newsrc' (Z s), on group exit, at article motion time, and at some other moments: it is *not* saved immediately merely because you read an article (that would be much too slow with some backends).
|
|
||||||||||||