Description of problem: Received a message into the inbox (I use mbox format) after upgrade to 2.2.12 package in testing. Attempted to move it to another folder in Evo. Evo reported a server error. Mail log had this: ----------------------- Feb 19 09:56:18 server dovecot: imap(user): Error: Corrupted index cache file / home/users/user/mail/.imap/INBOX/dovecot.index.cache: Broken physical size for mail UID 15753 Feb 19 09:56:18 server dovecot: imap(user): Error: Cached message size larger t han expected (8501 > 2113) Feb 19 09:56:18 server dovecot: imap(user): Error: Corrupted index cache file / home/users/user/mail/.imap/INBOX/dovecot.index.cache: Broken physical size for mail UID 15753 Feb 19 09:56:18 server dovecot: imap(user): Error: Cached message size larger than expected (8501 > 2113) Feb 19 09:56:18 server dovecot: imap(user): Error: Corrupted index cache file /home/user/mail/.imap/INBOX/dovecot.index.cache: Broken physical size for mail UID 15753 Feb 19 09:56:18 server dovecot: imap(user): Error: Cached message size larger than expected (8501 > 2113) Feb 19 09:56:18 server dovecot: imap(user): Error: Corrupted index cache file /home/user/mail/.imap/INBOX/dovecot.index.cache: Broken physical size for mail UID 15753 Feb 19 09:56:18 server dovecot: imap(user): Error: copy: i_stream_read() failed: Invalid argument Feb 19 09:56:18 server dovecot: imap(user): Error: Cached message size larger than expected (8501 > 2113) Feb 19 09:56:18 server dovecot: imap(user): Error: Corrupted index cache file /home/user/mail/.imap/INBOX/dovecot.index.cache: Broken physical size for mail UID 15753 Feb 19 09:56:18 server dovecot: imap(user): Error: mail parser: read(/home/user/mail/inbox, box=opensource/kernel) failed: Invalid argument ----------------------- Version-Release number of selected component (if applicable): dovecot-2.2.10-1.fc20.x86_64 How reproducible: Once. Steps to Reproduce: 1. Receive e-mail (using dovecot-pigeonhole to deliver to folders). 2. Attempt to move it to another folder in Evo. 3. See above errors. Actual results: Message would not move on the first attempt. Worked the second time, so maybe the index was somehow corrupted, although that would be the first time I've seen anything like this. Expected results: Worked with 2.2.10. Additional info:
Sorry, the version number that has a problem is, of course, 2.2.12-1 - not 2.2.10-1. I already downgraded when I ran rpm -q there.
History repeating? Bug #882387.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora 'version' of '20'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 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 this bug is closed as described in the policy above. 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.