Version: 1.9.1 (using KDE KDE 3.5.1) Installed from: SuSE RPMs OS: Linux When creating new IMAP-Folders within kmail it just brings an error. So I changed to unencrypted IMAP and snooped one session. The output is as follows: 2 CAPABILITY * CAPABILITY IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ MAILBOX-REFERRALS NAMESPACE UIDPLUS ID NO_ATOMIC_RENAME UNSELECT CHILDREN MULTIAPPEND BINARY SORT THREAD=ORDEREDSUBJECT THREAD=REFERENCES ANNOTATEMORE IDLE STARTTLS AUTH=GSSAPI AUTH=CRAM-MD5 AUTH=DIGEST-MD5 SASL-IR X-NETSCAPE 2 OK Completed 3 login ..... 3 OK User logged in 4 NAMESPACE * NAMESPACE (("" ".")) (("Other Users." ".")) (("Shared Folders." ".")) 4 OK Completed . . . 236 LIST "" ".Testordner" 236 OK Completed (0.000 secs 1 calls) 237 CREATE ".Testordner" 237 NO Invalid mailbox name 238 LSUB "" "%" * LSUB (\Noinferiors) "." "INBOX" * LSUB () "." "Admin" . . . So kmail just adds a dot "." in front of the folder-name. It should be like this: 237 CREATE "Testordner" The seperator should be left out (of course).
I've been wondering those dots also. I guess it has something to do with Maildir+ format. See http://en.wikipedia.org/wiki/Maildir (there must be better rfc or std for maildir, please refer one if you know such). I don't know should those appear in IMAP traffic or not. I'm using 3.5.1 KDE here and first I thought it was fixed but now again I cannot create folders.
According to RFC 3501: 6.3.3. CREATE Command Arguments: mailbox name Responses: no specific responses for this command Result: OK - create completed NO - create failure: can't create mailbox with that name BAD - command unknown or arguments invalid The CREATE command creates a mailbox with the given name. An OK response is returned only if a new mailbox with that name has been created. It is an error to attempt to create INBOX or a mailbox with a name that refers to an extant mailbox. Any error in creation will return a tagged NO response. Crispin Standards Track [Page 34] RFC 3501 IMAPv4 March 2003 If the mailbox name is suffixed with the server's hierarchy separator character (as returned from the server by a LIST command), this is a declaration that the client intends to create mailbox names under this name in the hierarchy. Server implementations that do not require this declaration MUST ignore the declaration. In any case, the name created is without the trailing hierarchy delimiter. If the server's hierarchy separator character appears elsewhere in the name, the server SHOULD create any superior hierarchical names that are needed for the CREATE command to be successfully completed. In other words, an attempt to create "foo/bar/zap" on a server in which "/" is the hierarchy separator character SHOULD create foo/ and foo/bar/ if they do not already exist. If a new mailbox is created with the same name as a mailbox which was deleted, its unique identifiers MUST be greater than any unique identifiers used in the previous incarnation of the mailbox UNLESS the new incarnation has a different unique identifier validity value. See the description of the UID command for more detail. Example: C: A003 CREATE owatagusiam/ S: A003 OK CREATE completed C: A004 CREATE owatagusiam/blurdybloop S: A004 OK CREATE completed Note: The interpretation of this example depends on whether "/" was returned as the hierarchy separator from LIST. If "/" is the hierarchy separator, a new level of hierarchy named "owatagusiam" with a member called "blurdybloop" is created. Otherwise, two mailboxes at the same hierarchy level are created. ------------------- This says nothing about a prefixed delimiter. Only trailing delimiters are ok. Especially this part is interesting: If the server's hierarchy separator character appears elsewhere in the name, the server SHOULD create any superior hierarchical names that are needed for the CREATE command to be successfully completed. In other words, an attempt to create "foo/bar/zap" on a server in which "/" is the hierarchy separator character SHOULD create foo/ and foo/bar/ if they do not already exist. This means if you have a prefixed delimiter the IMAP-Server tries to create an *empty* mailbxo which is not possible.
Strange, this should be fixed in 1.9.1 Any chance to try this with a current cvs checkout (3.5 Branch)? What server is this?
I may try with a current cvs some time this week. The Server is a cyrus imap (version 2.2.12) I report back of the results from the cvs.
Just compiled kmail from branches/3.5 Same result. I checked out the trunk also, but need to compile qt4.1 beforehand (and most probably kdebase and kdelibs). So this can take some time ...
BTW: I'm using dovecot and same symptoms.
*** This bug has been marked as a duplicate of 121843 ***