[Bug 147839] New: kmail fails to correctly observe the allowed flags on a shared imap mailbox

[ian at onlineloop.com]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147839         
           Summary: kmail fails to correctly observe the allowed flags on a
                    shared imap mailbox
           Product: kmail
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdepim-bugs kde org
        ReportedBy: ian onlineloop com


Version:           3.5.7 (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.1.2 
OS:                Linux

When reading a mail in a shared IMAP folder that has restricted permissions, KMail seems to fail to observe these permissions.  When the mail is read, KMail tries to set a number of flags for the message for which I get a permission denied error.  

I have compared the action to that of Thunderbird and seen that Thunderbird asks the mail server for the flags it is allowed to set, and stays within these limits.  KMail seems to not ask the server for which flags it can set.

I have two captures from Wireshark which I will attach which compare that actions of KMail and Thunderbird.  Please note that in both captures I have edited the capture to change my username and password to "xxxxxxxx" for my own personal security.

In the Thunderbird capture, you can see at packets 209 and 210 that Thunderbird is asking for "myrights" and gets "lrsipd" back, and later observes these rights when setting the flags for the message.  KMail appears to not ask the mail server about these rights at all, and just tries to set the flags it thinks it should set.

This problem has existed for quite some time through previous versions of KMail that I have used, however I was only able to recently confirm that this is a bug.