Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
evolution doesn't download some messages from imap, showing their bodies as zero size (and with zero size attachment of text/html)
Version-Release number of selected component (if applicable):
evolution-2.28.3-30.el6.x86_64
How reproducible:
frequently
Steps to Reproduce:
1. check ""Check for new messages in all folders" and "Automatically synchronize remote mail locally" in "Email account" -> "Receiving Options"
2. switch evo to offline mode
3. send (add) tens to hundreds of various messages (plaintext/html, with/without attachments, conversation roots/replies) to some folder
4. wait till evo finishes "checking for new mail" and "synchronizing mail locally for offline use"
5. put evo back offline
6. browse the messages
Actual results:
* some messages (up to half in my experience) is "downloaded" with just newline in message body and zero-length html body (aka only headers are downloaded locally but evo pretends that message bodies and attachments are downloaded as well)
* even after evo is put back online, it doesn't redownload the message on browsing the messages in the same folder
* the messages are downloaded again when user selects different message, navigates to other folder, navigates back and selects the message again
Expected results:
* all messages are downloaded fully (preferably in order of: displayed parts of currently selected message, all headers, all preferred bodies, all attachments, all alternative bodies)
* if some (part of the) message is not downloaded, evo marks it as such and tries to re-download it on first occasion (after first synchronization finishes)
Additional info:
This is really annoying when one wants to read bunch of emails while travelling with bad or no network connection.
Here [4] is updated build, evolution-data-server-2.32.3-7.1.el6. It contains patch from comment #5, enhanced with a print on evolution's console when there was hit the bug with zero-length files. It prints either
> camel_imap_message_cache_get: Ignoring empty file 'path-to-file'
or
> camel_data_cache_get: Reporting error on empty file 'path-to-file'
Thus if you run evolution from a terminal, then you can see whether the newly added code was used or not.
[4] https://brewweb.devel.redhat.com/taskinfo?taskID=5939719
I didn't encounter the bug over last three weeks. I've had much smaller chance to hit it though, as I almost never checked cached messages when offline...
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-1540.html