![]() Registered Member ![]()
|
Right, it is fine since I don't have any mails inside the top (or call it root) directory of "Local Folders".
What about the non-existing folder in "Local folder"? Actually, there are more than 3 "old" directories that where removed. Why are they not "synced"? |
![]() Registered Member ![]()
|
Hmmm.. Very odd behavior Nikos. Maybe others will give their experiences as to if this process works for them. I run kmail here on only one machine (using kubuntu) and the 'bulk selection - filtering process' seems to work ok on it. However, since I have only tested it on that one machine, I have pretty limited experience with it. I am running kmail version 4.7.3 here. Perhaps it is an OS related issue causing the selection process not to work. I suppose your bulk text selection works well in other programs there... yes? cheers Bill |
![]() Administrator ![]()
|
@NikosAlexandris: For the deleted but still existing in the directory folders? No idea I am afraid. My guess is that they have been marked as deleted but retained for other (unknown) reasons.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
![]() Registered Member ![]()
|
4.7.3 here too. Strangely, though, it seems it works for single threads, no matter how many messages pertain to a thread! |
![]() Registered Member ![]()
|
I guess I have to report this. I'll wait a few days, and try to read more reports. Either I will post into an already existing "bug" report or open a new one. Cheers! |
![]() Registered Member ![]()
|
...and now is almost July and the problem with KMail and Akonadi is the same as is not worst...
|
![]() Registered Member ![]()
|
Before releasing a programm which is part of the well known KDE Desktop Environment with many happy users around the globe,
a DEVELOPER team should also Be considerate And objectively consider the state of the program: - if there's safe reliable migration process, - if there's still potentially serious problems that can lead to dataloss, - if there might still be regressions and whether they are openly and fairly documented and described Be respectful - respect your users trust - warn them for problems - respect the reputation of your fellows at KDE, the linux community and the linux ecosystem as a whole - respect the frustration of people that trusted in "stable" and "part of KDE" by fixing asap Be collaborative - By addressing the forums here and then and explaining your motives, your efforts and what can be expected and what not ... KDE is not a multibillion dollar business, you can stay in contact with your userbase! - advise and inform the distributions NOT to use the kontact suite, cause otherwise they potentially letting down their casual users to a "linux with KDE could be cool, but you can't use it productively, - better wait a few years..." experience. Be pragmatic - submit a "state of the software" post here and then, so people have a basis for deciding before installing ... - don't push stuff that's not completely worth it into "stable" to avoid all the troublesome, energy draining and timewrecking disussions (aren't we all mad about MS using ther paying(!) customers as betatesters?) - ask for more help if things go so terribly wrong as they did, there's no shame in that and many users willing to do everything to get some of the wort issues fixed So that would be a nice move on the developing side of the matter. I guess people ranting in the forums like me are often frustrated because in spite of the community idea the KDE forums often feel like a traditional nondisclosing company: you never get the responsible guys on the phone! just my two cents, thx for reading, piedro |
![]() Registered Member ![]()
|
Very well said, piedro
|
Registered users: Baidu [Spider], Bing [Bot], Google [Bot]