Summary: | kmail unuseable with cyrusIMAP - on reading mail KMail tries to set more flags than just SEEN | ||
---|---|---|---|
Product: | [Unmaintained] kmail | Reporter: | Giuseppe Ravasio <giuseppe_ravasio> |
Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | major | CC: | bjoern, bruno.leon, bugs, dreamer, kfunk, lemma, roby.secchi, rsecchi |
Priority: | NOR | ||
Version: | 1.9.9 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Giuseppe Ravasio
2008-03-14 11:36:18 UTC
I can confirm this bug. Version: 1.9.9 (KDE 3.5.10) Installed from: Debian Lenny Cyrus Imapd Version: 2.2.13 This bug is also relevant using kmail 1.11. This might be a duplicate of bug 159296. This might be a duplicate of bug 147792. (ignore the previous comment please) Sorry.. utter confusion. I meant: This is probably a duplicate of bug 147839 (Permissions for allowed flags for IMAP account not obeyed). c#3 and c#4 are utter nonsense. This bug is more than ONE year old, a serius issue that makes Kmail UNUSABLE in most cases and no one is even taking it in account! Vey good The same bug is present in the KMail Version 1.11.0 packaged in KDE 4.2.00 (KDE 4.2.0) on Ubuntu 8.10... Roberto I'm using kmail in conjunction with cyrus imap server. Again after the last update of kde-pim package on Ubuntu jaunty. ii kmail 4:4.2.2-0ubuntu1 rc kmail-kde3 4:3.5.10-0ubuntu2~intrepid1 rc kmailcvt-kde3 4:3.5.10-0ubuntu2~intrepid1 the error again from UI is: "Error while uploading status of messages to server: Changing the flags of message imaps://me@mbox.modiano.com:993/sysadmin/sysmdn/;UID=58380 failed with NO." I've "lrs" permissions on folder "sysmdn" that's mean "list, read, seen". Quote for Ravasio, the situation is the same as him. Kmail try to set flags in imap folder. (DRAFT Flag I think). In our business scenario the resolution of this bug is very important.... ;-) Toc Toc 2010 is here sitting aside this bug. Two years passed away and I'm starting feeling home with gnome firefox and thunderbird... I miss my beloved kmail (and kde and konqueror) Giuseppe Hello guys... AGAIN... in the 4.5.0 Version of Kmail I cannot read emails in a folder shared if I don't have the write permissions... what a joke... I want only read email ! ... The strange situation is that we ha 200 thunderbird working in kde enviroment instead of kmail for this problem. ... --- ... Roberto. Confirming the bug is still present in KMail 1.13.5, that's sad... kioslave/imap4/imap4.cpp IMAP4Protocol::special function on change status case ---- 01355 // make sure we only touch flags we know 01356 QByteArray knownFlags = "\\SEEN \\ANSWERED \\FLAGGED \\DRAFT"; 01357 const imapInfo info = getSelected(); 01358 if ( info.permanentFlagsAvailable() && (info.permanentFlags() & imapInfo::User) ) { 01359 knownFlags += " KMAILFORWARDED KMAILTODO KMAILWATCHED KMAILIGNORED $FORWARDED $TODO $WATCHED $IGNORED"; 01360 } 01361 01362 CommandPtr cmd = doCommand (imapCommand:: 01363 clientStore (aSequence, "-FLAGS.SILENT", knownFlags)); --- How about to remove \\ANSWERED \\FLAGGED \\DRAFT flags ?!?!?! Git commit 81897c5c0a188ff6dc9933ce30c2cc3215f85323 by Andre Heinecke. Committed on 19/09/2013 at 16:26. Pushed by aheinecke into branch 'enterprise/e3'. Only update SEEN flag when it is the only allowed If the server says in the select command that a folder is read-write Kontact assumes that it can modify a basic set of flags. (See the bug for more info) But if we can only modify SEEN we can reuse the setSeenFlags functions. This is a bit of a workaround for a proper and generic handling of the permanentFlags but since this is only relevant for the old code I did not want to change more then necessary to solve the concrete Problem. Fixes: kolab/issue4868 M +5 -1 kmail/kmfolderimap.cpp http://commits.kde.org/kdepim/81897c5c0a188ff6dc9933ce30c2cc3215f85323 Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback. |