On Fri, 2002-12-20 at 18:36, Toshiro wrote: > > > Yes. I have tried other mail clients and have always gone back to Kmail. > > > It has never ever crashed on me or given me any problems. I have also > > > used pine, evolution (yuck...and no way to order mail by date?), > > > > don't know what beta you were on, but 1.0.2 orders by date by default. > > Also supports threading and has a pretty nifty search function. > > > > Well, the handling of threads in Evolution sucks (to say the least); have you > tried to delete the first mail of a thread? when you do that, the cursor > moves to wherever it wishes (instead of positioning in the next unread > mail). >
Actually it just selects the next message in the thread, using 1.0.8[3mdk]. I've never used any Evolution version pre-1.0, and I've never seen any of the things people have been complaining about in this thread. I do know it's not a very good IMAP client, but this doesn't affect me as I think IMAP is a rather sucky[1] protocol and I don't use it. I've also had some instability in each of the Evolution modules, but it's always been limited to that module -- I just get a little popup stating that Contacts unexpectedly quit, or I can't view the summary page. oaf-slay fixes it. I will unequivocally state that the evolution-pilot conduits suck rocks, to the point of actively being worse than having no synchronization capability at all. Jpilot is the only way to realistically manage PalmOS in my experience, which is a shame (Jpilot is great, but nonintegration of your PDA with other contacts and calendar is an issue). > The very bad handling of threads is the reason I quit using Evolution. > To each his own -- I gave up using mutt because the config file was a monolithic cruftpile on the order of sendmail.cf or procmailrc, a reason at which mutt aficionados will only sneer. I gave up on kmail because it would grab duplicate copies of mail from the local /var/spool/mail/user and had zero integration with kpilot (a pile of junk in its own right at the time). KDE fans will leap to assure me that it's all fixed now and if it isn't I can surely rearrange my needs to meet kmail's requirements :-) [1] The thing I dislike about IMAP is its fundamental design and reason for existence, which is the idea that my mail should stay on the server and get copied to my client. If I want the mail to stay on the server, I'll leave it there in an mbox or maildir and access it with a local client over an encrypted tunnel. If I want it on my desktop, I want it to get here as fast as possible and be deleted from the server because it's no longer necessary there. This design problem leads to all the implementation problems of IMAP: SLOWness, lack of integration with local folder structures, and muddling of GUIs for rule-creation, mass copy or delete, etc. -- Jack Coates Monkeynoodle: A Scientific Venture...
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
