Summary: | KMail tries to annotate a read only folder | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Thomas Zander <zander> |
Component: | commands and actions | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | chrigi_1, kollix, montel, vanmeeuwen |
Priority: | NOR | ||
Version: | 4.9 pre | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Thomas Zander
2009-02-28 11:11:35 UTC
You're right - it shouldn't. However, the folder isn't entirely read-only - you seem to have 'admin' rights. Regrettably, 'admin' rights do not imply 'the other rights' which would still need to be set explicitely (by an admin). Christian, I feel I have confirmed before this is no longer an issue in current KDE, but I would appreciate your confirmation. Note sure why you got in that situation in the first place (I couldn't find the relevant codepath), but I don't think it can happen with the current kolab resource. Once an annotation has been erroneously set on a akonadi-collection without modify rights though, the imap resource indeed tries on every sync to write it to the server. I'm not quite sure yet though how to resolve that in the imap resource(if at all) . As a workaround you can delete the annotation using akonadiconsole: Browser Tab -> Rightclick -> Folderproperties -> Attributes tab -> edit the folderannotations. The admin rights do not play into the behaviour, it's just that ACL rights in akonadi are not enforced and clients need to check themselves (which the kolab resource obviously didn't). Lets close this one now :) |