Summary: | kmail2 does not allow creation of new top-level folder | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Andrey Borzenkov <arvidjaar> |
Component: | folders | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | amantia, antonis.tsiapaliokas, bruno, bugs.kde.org, dglent, dmitry.torokhov, jon, kdudka, kumaran, m00nraker, montel, pancho.s, pete, stephan.diestelhorst, _hamlet |
Priority: | NOR | ||
Version: | 4.9.1 | ||
Target Milestone: | --- | ||
Platform: | Mandriva RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Andrey Borzenkov
2010-09-19 07:03:12 UTC
I encountered this same behavior on KDE 4.6 RC2. Confirmed. Confirming on KMail 2.1.0 (KDE 4.6.4, Gentoo) too. Note that on akonadiconsole the same feature is enabled (i.e. it is possible to create such top-level directories). Hello This bug is still valid on kmail 4.8 pre. I have create a patch which is solving this issue. https://git.reviewboard.kde.org/r/102031/ *** Bug 279116 has been marked as a duplicate of this bug. *** "KMail Folders" sounds like a migrated mixedmaildir account. Reassigning. Comment #3 says it is possible in Akonadiconsole, suggesting that is not caused by the resource but by additional access restrictions in KMail This is a pretty serious assumption made about IMAP. I will never roll out kmail2/akonadi until this is addressed. My reasons are detailed in this related bug: https://bugs.kde.org/show_bug.cgi?id=292418 Please take this issue seriously. I'm not about to take on the headache of educating my users as to why they can do it on just about every other device or piece of software and not in kmail2! (In reply to comment #8) > This is a pretty serious assumption made about IMAP. I will never roll out > kmail2/akonadi until this is addressed. My reasons are detailed in this > related bug: https://bugs.kde.org/show_bug.cgi?id=292418 > > Please take this issue seriously. I'm not about to take on the headache of > educating my users as to why they can do it on just about every other device > or piece of software and not in kmail2! F.Y.I: KDE 4.8.2 on Kubuntu Oneric from official Kubuntu PPAs. Note that the original issue was reported for mixedmaildir and not for IMAP. Please do not mix that. OTOH I can assure that creation of toplevel folders works fine for maildir. My apologies. The IMAP issue has been open for quite a while and there doesn't seem to be much comment on the issue by developers. My frustrations are spilling over. This is the only issue preventing our roll out and the heat of delay falls on me. (In reply to comment #10) > Note that the original issue was reported for mixedmaildir and not for IMAP. > Please do not mix that. OTOH I can assure that creation of toplevel folders > works fine for maildir. *** Bug 301100 has been marked as a duplicate of this bug. *** It's fixed in 4.8.5/4.9 I have KDE 4.8.5 now and it does nt work here I create a folder, the folder it is created in gmail (i verified from the browser) but i dont have the new folder. I totaly rebooted the computer without success, the new folder does not exist in kmail (but it is present in gmail) on kde 4.8.5 (openSUSE 12.1 + kr:48 repository) Here on a pure dovecot imap account, add a folder seems to be possible (the ui permit it) but once the name is entered the new folder is not visible in kmail2 ... trying to refresh the local subscription lead to nothing. Using my webmail account the folder is there, but in the meantime I get an akonadi error unable to create collection 14 ... 01_bruno: Unknown error. (Could not create collection testng resourceId: 14) which is the name of the new folder ... I repeat with the webmail no trouble at all..... w00t this bug doesn't seems to be totally fixed. Trace, debug on request (tigerfoot on irc) with a step by step instruction should be possible to give. Confirmed, bug still not resolved. Still not possible to create top level folder (dovecot imap server). Using KDE 4.9.1... Reopening based on comment #16 How do this one and Bug #292418 relate to each other? They seem to be similar enough to mark this a duplicate of the other one, even though this one is older. The other one here has the commits though. Please, don't report IMAP problems here. This was for *mixedmaildir*. For imap, see bug 292418. Reopen only if you see the problem for mixedmaildir accounts. If you see with IMAP (with 4.10.2), reopen the other bug. |