Summary: | Update bug when using (disconnected) imap resource | ||
---|---|---|---|
Product: | [Applications] korganizer | Reporter: | Stéphane Magnenat <stephane> |
Component: | groupware | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | major | CC: | lav, smartins |
Priority: | NOR | ||
Version: | 3.4.1 | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Stéphane Magnenat
2005-09-29 09:59:15 UTC
Ah, so I'm not alone! I tried to debug the problem with Till Adam a while ago and it seems that immediately after uploading a message to the mail server, the mail server does not report this message as existing. Thus it is removed locally in kmail (although it is actually on the server). Only after a short while the mail server reports the mail in his message list (second sync), and then it is re-downloaded again to the local cache. BTW, I have a courier imap server, version 3.0.8. I agree that this gives a very bad impression on korganizer / kontact as it seems that some entries are simply lost. I was confused more than once by this problem. Cheers, Reinhold I'm also using courier 3.0.8 (3.0.8-4sarge2), perhaps it is a courier bug. Does anyone knows if it works fine with others imap servers? What do you think? Should we report it as a courier bug? Steph I've reported this bug to the Debian bug tracker system as Bug#334045 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334045) Steph It is no courier bug, I see the same behaviour with uw-imap. Just for information, problem is still present in KDE 3.5.1. Debian people tend to say it's not an imap server bug but rather a missinterpreted specified behaviour in the client. I hope this bug will be fixed soon as it's a quite disturbing behaviour. Thanks Steph The problem is still in KDE 3.5.5 Reassigning all KOrganizer bug reports and wishes to the newly created korganizer-devel mailing list. Is there any progress with this bug? It render the use of kmail groupeware features quite unstable. Is this still an issue with korganizer 4.2 ? The bug seems fix in the sense that the event disappear but reappears within one second. While this behavior is not very nice, it is certainly acceptable. (In reply to comment #11) > The bug seems fix in the sense that the event disappear but reappears within > one second. While this behavior is not very nice, it is certainly acceptable. Ok, closing then. I also think akonadi fixes this. I can't reproduce. |