Summary: | IMAP add folder creates .FOOBAR but stored in akonadi database as /FOOBAR | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Patrick Noffke <patrick.noffke> |
Component: | commands and actions | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | major | CC: | dvratil |
Priority: | NOR | ||
Version: | 4.10.5 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
URL: | http://forum.kde.org/viewtopic.php?f=215&t=109833 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Patrick Noffke
2013-10-05 12:18:12 UTC
Dovecot automatically prefixes all folders on filesystem with ".". The important thing is, what separator does it uses in IMAP communication and I'm pretty much certain Dovecot uses "/", unless you have configured it otherwise. (You can verify this by connecting to the server: openssl s_client -connect mail.server.com:imaps, sending "0 LOGIN username password" and then "1 LSUB "" "*"" and checking whether the fourth column says "/" or ".") From what I can see in the forum, there are two bugs being hit: wrong remoteID for top-level folder and using "/" separator for IMAP servers that use ".". The first problem was fixed in 4.11, the second will be fixed in next 4.11.x release. If you can, please test with latest version of 4.11 and close this bug if it's fixed. The fourth column is a ".". I didn't explicitly configure this in dovecot. In my /etc/dovecot/conf.d/10-mail.conf file, there is an "inbox" namespace, with the separator field commented out. In fact, everything is commented out in that section except "inbox = yes". So I'm guessing the default is "." unless it is explicitly set otherwise. I will probably upgrade to fedora 19 relatively soon. That would be the earliest I could try 4.11 (assuming they are at 4.11 in that version). This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |