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 745742 - Attachment with Content-Type: application/x-shellscript not shown in email viewer
Attachment with Content-Type: application/x-shellscript not shown in email vi...
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2015-03-06 13:09 UTC by c.kirbach
Modified: 2015-03-09 11:58 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
email editor (75.32 KB, image/png)
2015-03-06 13:09 UTC, c.kirbach 		Details
minimal test case: no body but just one shell script attachment. (1.45 KB, application/mbox)
2015-03-06 13:11 UTC, c.kirbach 		Details

Description c.kirbach 2015-03-06 13:09:32 UTC 
Created attachment 298706 [details]
email editor

Evolution 3.12.11

Attachments with Content-Type: application/x-shellscript are not shown in the email viewer. there should be an expander (+) in between the email headers and the email body test for any attachment, but it is missing.

Other email content like the message text is shown as expected, and other attachment types like image/png are also shown as expected with an expander.

Attaching the full source of an example mail. It has a shell script attached as multipart.
Comment 1 c.kirbach 2015-03-06 13:11:14 UTC 
Created attachment 298707 [details]
minimal test case: no body but just one shell script attachment.

minimal test case: no body but just one shell script attachment.
Comment 2 Milan Crha 2015-03-09 11:58:25 UTC 
Thanks for a bug report. Your test message does not contain any attachments, I guess it's a typo (wrong messages attached). Nonetheless, I was able to create one test message myself and I see it working properly in the current development version. It had been fixed by commit a4af2d6aeefa48bf8a, which missed 3.12.11.