After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 763280 - Multipart emails not read properly from server
Multipart emails not read properly from server
Status: RESOLVED DUPLICATE of bug 761096
Product: evolution
Classification: Applications
Component: general
3.18.x (obsolete)
Other Linux
: Normal major
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2016-03-08 02:21 UTC by James
Modified: 2016-03-08 11:57 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description James 2016-03-08 02:21:41 UTC
Multipart emails (typically with attachments) are regularly broken when received from Google via IMAP.

Evolution also doesn't seem to provide a way of refreshing the email. Viewing a message source often appears like so:

X-Evolution-Source: 1433296179.1305.15@*removed*
Date: Tue, 08 Mar 2016 10:07:46 +0800
Subject: No Subject
Message-ID: <1457402877.1870.15.camel@*removed*>
Mime-Version: 1.0
From: 

OR

X-Evolution-Source: 1449160844.14056.2@*removed*
Date: Tue, 08 Mar 2016 10:14:30 +0800
Subject: No Subject
Message-ID: <1457403270.1870.16.camel@*removed*>
Mime-Version: 1.0
From: 

--_009_6fe7d2af2dab464585613dbaadb0e521SYDEXCH1ARlocal_--


When grabbed from another machine running Evolution, there is a 50/50 chance it will work fine. Otherwise I have to login via gmail to retrieve the message.

This bug has existed for over a year, and seems to show itself at least once or twice a week, regardless of connection quality or build. A workaround that doesn't involve clearing evolutions entire cache would be acceptable.
Comment 1 Milan Crha 2016-03-08 11:57:46 UTC
Thanks for a bug report. It's not needed to clean up whole cache, just locate the broken message there and delete than one file. Selecting the message again will download it as well.

As you mention Google, it seems to have issues when there are many concurrent connections setup and when it downloads large messages in chunks (multi fetch). 

I think of changing the default to disable multifetch and prefer download of the messages at once. Users with already defined accounts may not notice the change, if they have the value already saved in the file, thus it can help to re-configure the account from scratch or edit the corresponding .source file as described at a downstream bug [1]. It also references bug #761096, thus I'm moving this there.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1306846#c9

*** This bug has been marked as a duplicate of bug 761096 ***