| |||||||||||||
The Grumpy Editor reviews Claws MailThe Grumpy Editor reviews Claws MailPosted May 29, 2008 19:59 UTC (Thu) by cventers (subscriber, #31465)In reply to: The Grumpy Editor reviews Claws Mail by rfunk Parent article: The Grumpy Editor reviews Claws Mail
Fellow KMail user here. For my email, I find that KMail is the least annoying mail client. The font rendering is good, and the layout and icons are decent. It doesn't seem to butcher diffs the way other mail clients do. Two things drive me crazy about KMail. The first is that it does, on rare occasions, crash. It's not nearly as bad as Konqueror, which I also use because I find it the least annoying... but it does still crash. :( The other issue is a behavior I've seen when KMail starts juggling a lot of messages over IMAP. Eventually, it seems that the cache gets corrupted such that the message header list won't match with the actual message list. In other words, you end up with surprising behavior in which you go to click a header (or key to it) and find that the message KMail has loaded is completely different. Generally, the header you click will change to match this message as well. The confusion gets even worse when you try to use the Search feature to search the message headers... In these instances, I've found that nuking all of the IMAP cache with rm -rf is the only way to fly.
(Log in to post comments)
KMail Posted May 29, 2008 20:15 UTC (Thu) by rfunk (subscriber, #4054) [Link] Yes, I've noticed similar behavior, except that the list-cache issue is more likely to give me empty messages than wrong messages. Strangely, it's a much bigger problem on one of my machines than on the other, despite them running the same version of Kubuntu (though different kernels). I eventually got tired of nuking the IMAP cache on the one machine, and now use KMail only on the other one. :-/ Konqueror's crashes seem to be most often due to memory overload or (more rarely) javascript oddities. It doesn't leak memory as badly as Firefox does, but it does leak memory worse than I'd like.
KMail Posted Jun 7, 2008 13:38 UTC (Sat) by Duncan (guest, #6647) [Link] > Konqueror's crashes seem to be most often > due to memory overload or (more rarely) > javascript oddities. It doesn't leak > memory as badly as Firefox does, but it > does leak memory worse than I'd like. Hmm, maybe that's why I don't tend to see such crashes. I keep scripting off by default and finally have plenty of memory (8 gigs, 64-bit environment). The problem then is that konqueror severely lacks sufficient scripting control, similar to noscript on iceweasel. I can turn scripting on for a particular site and often, scripted features I want still won't work, because the script is loaded off a different site. With iceweasel, it's simply a matter of checking noscript to see what additional sites the page is trying to load scripts from and enabling the ones one wishes (view the scripts first using the jsview extention if desired) either temporarily or permanently. With konqueror, I'd have to either view source and check manually for scripts loaded from other sites, then load konqueror's scripting config and manually type in and enable all the desired sites individually (and permanently until deleted, no temporarily enable option available), or give up and enable scripting globally, including for sites like google analytics (urchin tracker) that I'd normally ban. That's the big reason I still keep iceweasel around. If konqueror were to get decent with its scripting control, using extensions or built-in, I'd likely be able to give up iceweasel entirely. It's possible there'd still be some compatibility issues, but where I've dared to, many of those magically disappear if I enable scripting globally in konqueror. Duncan
The Grumpy Editor reviews Claws Mail Posted Jun 1, 2008 20:34 UTC (Sun) by quotemstr (subscriber, #45331) [Link] 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.
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).
|
|||||||||||||