Hide Forgot
Created attachment 1198339 [details] Evolution error with mailing list email. Description of problem: Evolution is not handling messages with links that use the mail:// url format typical in mailing list emails. When clicking on one of the links in the email you get an error stating: Could not open link and instead it should take you to the particular section of the email message. A screenshot of the issue is attached. This works fine on newer version of Fedora but not in RHEL. Version-Release number of selected component (if applicable): evolution-3.12.11-15.el7.x86_64 How reproducible: Always. Steps to Reproduce: 1.Open email with links that use mail:// url format 2.Click one of the links 3. Actual results: Expected results: Additional info:
Thanks for a bug report. This specific error comes from the gvfs, where the URL had been passed to. Would it be possible to attach here an example message for testing, please?
I can definitely do that. What format do you want? Just the html of the message or it looks like I can save the message as an mbox file as well.
The mbox file is better. Simply right-click the message in the message list, pick "Save as mbox" and then choose a file to save to. Edit the file and "censor" anything private from it before attaching it here. Thanks in advance.
Created attachment 1198776 [details] Email message with mail:// urls. There is nothing sensitive in this email so no worries there.
Thanks for the test message. They use references like <a href="#a5"> which means "jump to the section named 'a5' in this document. The "mail://" is an evolution custom protocol, which surprised me to be part of the message itself. The Fedora version
Oops, I sent the comment too early, I'm sorry. The related upstream commits are: https://git.gnome.org/browse/evolution/commit/?id=5306c9f8b0 https://git.gnome.org/browse/evolution/commit/?id=0979bb96d
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. https://access.redhat.com/errata/RHBA-2017:2066