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.

Created attachment 628401 [details]
message in question

Description of problem:
Evolution when it gets to the attached message just stops on the attached message, it gets to 100%CPU on one CPU (fortunately, I have more of them) and that's it.

Version-Release number of selected component (if applicable):
evolution-3.6.0-1.el7.x86_64

How reproducible:
this message has never been succesfully parsed even though I have killed and restarted evolution couple of times (including removing whole cache of the folder where the message is located ... it's on IMAP, against Zarafa server).

Steps to Reproduce:
1.see attached evidence
2.
3.
  
Actual results:
see above

Expected results:
message should be pretty quickly parsed and I go on with my life.

Additional info:

Created attachment 628402 [details]
screenshot of the Evolution in the given state

Created attachment 628405 [details]
~/.cache/gdm/session.log

Created attachment 628406 [details]
backtrace of evolution when the thing happened

Thanks for a bug report. I can reproduce it with your message too.

I filled this upstream [1] for a better reference, and took your message, stripped from it private information, and attached it there for testing too.

[1] https://bugzilla.gnome.org/show_bug.cgi?id=686278

Fixed within upstream bug for 3.6.2. I thought it's because multipart/mixed, but it turned out as a problem with prefer-plain plugin, which broke the parts list (probably because text/plain part was after text/html, while it should be the fist part).