Bug 319842 - KMail ignores negative acknowledgements from IMAP server
Summary: KMail ignores negative acknowledgements from IMAP server
Status: RESOLVED DUPLICATE of bug 328393
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: GIT (master)
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-14 19:57 UTC by Christopher Yeleighton
Modified: 2013-12-03 17:46 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Yeleighton 2013-05-14 19:57:08 UTC 
When my IMAP account is over quota, moving messages around fails because the server has to copy them first.  All other IMAP clients I tried (Seamonkey, Thunderbird, Windows Mail) inform the user about the failure and leave it where it was.  KMail pretends that it has been moved; it reappears when the folder content is refreshed.

Reproducible: Always

Steps to Reproduce:
1. Move a mail message from folder A to folder B.

Actual Results:  
1. Message disappears from folder A.

Expected Results:  
1. Server refused: OVER QUOTA.
Comment 1 Laurent Montel 2013-06-08 12:00:18 UTC 
Ok we need to test it.
Don't know if we test it.
We need to investigate it.
Comment 2 Kevin Ottens 2013-11-16 07:33:07 UTC 
The IMAP resource has a new maintainer, reassigning to him.
Comment 3 Christian Mollekopf 2013-12-03 17:46:49 UTC 
This is a conceptual limitation of akonadi. Since operations are executed against the local cache, the resource cannot immediately object until it synchronizes to the server.
However, the imap resource should in this case inform the user using a notification that the action failed.
Ideally we could also catch the error immediately by comparing the stored quota limits, but that's another story.

So for now this becomes a duplicate to notify the user about errors.

*** This bug has been marked as a duplicate of bug 328393 ***