https://bugs.kde.org/show_bug.cgi?id=275233
--- Comment #3 from S. Burmeister <sven burmeister gmx net> 2011-07-12 13:11:35 --- I might have some hints towards reproducing this. - Create filters that move emails from your imap inbox to local folders - Mark some threads that still receive emails as "ignore" on that box - change the local folder, e.g. open the trash - use another computer to access the same imap account (no filters) with kmail and read some of the messages that are going to be marked as ignored on the other box. (- while the messages are already moved (status unseen) to a local folder on the first box the second one can still access them until the account is checked again, maybe because akonadi cached them) [this is optional] Second scenario: - set-up filters to move email to a local folder on one box - retrieve emails with that box. kmail will only download their headers and show them in the list - next kmail will try to download the content of the emails to filter them, i.e. the content is not yet available to kmail and clicking on one of them would start to download the content - make your internet connection fail, i.e. no traffic but no disconnection either - now restart akonadi or kmail, suspending might already do the trick, maybe even going offline and online. - next time kmail will try to retrieve the emails it might succeed and retrieve the full email - however there will be a conflict because apparently the email (only headers) does already exist and thus the version conflict window shows the first attempt email as empty, i.e. no data and the second with full content and a date/time-stamp of some minutes later than the first one. The second example would only make sense if my assumption is correct that the version conflict GUI does not show headers but only the "full payload" including headers. I have logged what happens if such a conflict comes up. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list [email protected] https://mail.kde.org/mailman/listinfo/kdepim-bugs
