Description of problem: Yesterday, I had Evo crash when I sent another piece of e-mail through the dovecot server to myself form K9-Mail. The logs had this to say about it: ------------------- Nov 30 13:00:08 machine dovecot: imap-login: Login: user=<user>, method=GSSAPI, rip=RIP, lip=LIP, mpid=mpid, TLS, session=<blah> Nov 30 13:00:18 machine dovecot: imap(user): Error: Cached message size larger than expected (3104160 > 3101331) Nov 30 13:00:18 machine dovecot: imap(user): Error: Corrupted index cache file /home/user/mail/.imap/Sent/dovecot.index.cache: Broken physical size for mail UID 21614 Nov 30 13:00:18 machine dovecot: imap(user): Error: read(/home/user/mail/Sent) failed: Input/output error (FETCH for mailbox Sent UID 21614) Nov 30 13:00:18 machine dovecot: imap(user): Disconnected: Internal error occurred. Refer to server log for more information. [2012-11-30 13:00:18] in=3145045 out=3144800 ------------------- So, somehow sending a relatively big e-mail (a picture) from my Android phone, through dovecot, while Evo was also connected to it, caused this. Not sure what happened there - never seen this before. Version-Release number of selected component (if applicable): dovecot-2.1.10-2.fc17.x86_64 How reproducible: Happened only once. Steps to Reproduce: 1. See description. Actual results: Dovecot disconnected Evo, which had to rescan all the folders on restart. Expected results: Two clients should be able to use dovecot at the same time. Additional info: My mail is in mbox files. Evo using IMAP+. K9-Mail using whatever IMAP protocol it uses.
One more detail. Shortly after sending that piece of mail from K9-Mail, I deleted it in Evo. Not sure if that somehow confused dovecot. I do not see how it could - all these operations are supposed to be atomic, right?
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.