Bug 724723

Summary: Kmail can't create folders with hierarchy delimiter "/"
Product: [openSUSE] openSUSE 11.4 Reporter: Peer Heinlein <p.heinlein>
Component: KDE4 ApplicationsAssignee: E-mail List <kde-maintainers>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Critical    
Priority: P5 - None CC: ctrippe
Version: Final   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE 11.4   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Should be "Kontaktdatenbank/Bounce..." instead of "Kontaktdatenbank.Bounce..."

Description Peer Heinlein 2011-10-17 21:45:06 UTC
Created attachment 457129 [details]
Should be "Kontaktdatenbank/Bounce..." instead of "Kontaktdatenbank.Bounce..."

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20100101 Firefox/7.0

Most of the IMAP-servers use "." as hierarchy delimiter. But for several reasons it's very usefule to use "/" instead.

Kmail isn't able to work with IMAP-servers havine a "/" as hierarchy delimter. 

In this cases, KMail isn't able to create new folders, because there is a hard-coded "." in the new folder-name, as you can see in the attached screenshot.

This bug makes it unimpossible for normal users to create new folders!

If necessary I can provide test accounts on a dovecot 2.0-server having a "/" hierarchy delimter. Just mail me at p.heinlein@heinlein-support.de





Reproducible: Always

Steps to Reproduce:
1. Make Dovecot using "/" as delimter in its IMAP namespace
2. use kmail
3. create a folder
Actual Results:  
IMAP-error, because kmail send's a folder path having a "." in it
Comment 1 Peer Heinlein 2011-10-28 16:02:54 UTC
If Kmail can't create the new folder, but mails are already moved into this folder on the client, a data loss ist possible. => Severity CRITICAL.

kmail is an important application, working with kmail is NOT possible at all in this sitations. PLEASE FIX.
Comment 2 Christian Trippe 2012-11-15 20:31:40 UTC
openSUSE 11.4 is no longer supported. If the problem still exists with newer KDE versions, it would be the best if you would report it upstream at bugs. kde.org. Thanks.