On Tuesday 18 June 2013 04:51:02 Malte Gell wrote:
Am 17.06.2013 17:03, schrieb Bob Williams:
In the early days of Kmail2 I migrated to Thunderbird, as I couldn't get the 'new' Kmail to work.
Time passes, and so yesterday I thought I'd give Kmail another look. It had remembered my IMAP mail server settings, and imported the folder structure, so setting it up was no problem, and it downloaded all the mail.
However, all the new mail was dumped in the Inbox, despite there being a comprehensive set of active filters.
Bob, in my mind Kmail2 is broken, totally. It is not worth to give it a second chance. Like you I migrated to Thunderbird. I use IMAP as well and it works fine with Thunderbird. The only thing I miss with Thunderbird is the ability to invoke a command from a filter and to filter outgoing email. Besides that, Thunderbird just does it, it is a reliable workhorse. I do not recommend do depend on Kmail2 for serious work.
Malte
As you're probably aware, there are about 1.000.000 different ways of using KDE PIM. It is extremely hard to support all these use cases - and you can not expect the developers (who, after all, only represent, use and develop a sub set of these features) to extensively test and work on each and every thing. Some scenario's are simply more stable than others. See this mail from Georg about the current state: http://lists.kde.org/?l=kde-pim&m=136791444006823&w=2 In short, he states that the 'corporate' use case of IMAP + serverside filtering is completely stable and well supported. Anything else depends on volunteer help with testing, identifying issues and fixing them. Of course, a way of solving the problem would be to ONLY release Kmail with code for the use cases which are entirely stable and tested. Remove all other features... But how would people react to that? It might be better to just try to get those features stable, and that is of course being worked on. But it is a lot of work, don't under estimate it. So many factors interplay with so many others... PIM is hard. /J