Bug 30488

Summary:	Evolution: responding to/forwarding HTML messages converts formatting commands to plain text. FIX AVAILABLE
Product:	Mageia	Reporter:	aguador <waterbearer54>
Component:	RPM Packages	Assignee:	Olav Vitters <olav>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	Keywords:	UPSTREAM
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
URL:	https://gitlab.gnome.org/GNOME/evolution/-/issues/1918
Whiteboard:
Source RPM:	evolution-3.44.2-1.mga9.src.rpm	CVE:
Status comment:
Attachments:	Screenshot showing formatting commands

Description aguador 2022-05-27 19:03:13 CEST

In prior versions (through 3.44.1) of Evolution it was possible to have the basic message style set to Plain Text and either to an HTML message in plain text or to recover HTML formatting when responding. Now HTML formatting commands are converted to plain text and formatting is not recoverable.

To reproduce

1) Set Plain Text in the style (Preferences > Editor preferences)
2) Select an HTML message that has been received and either a) reply format or b) forward "in-line".
3) The body of the original HTML message will show with the formatting commands as plain text -- and, of course, the formatting cannot be recovered if the response is changed from Plain Text to HTML.

Will send a screenshot and enquire on the Evo ML.

Comment 1 aguador 2022-05-27 19:04:09 CEST

Created attachment 13279 [details]
Screenshot showing formatting commands

aguador 2022-05-27 19:19:15 CEST

Summary: Responding to/forwarding HTML messages converts formatting commands to plain text => Evolution: responding to/forwarding HTML messages converts formatting commands to plain text

Comment 2 Lewis Smith 2022-05-27 21:54:52 CEST

Thank you for the report.

As this is a change in behaviour from 3.44.1 to 3.44.2, this suggests an upstream problem.
 evolution-3.44.1.tar.xz	12.5 MiB	2022-Apr-22 06:08
 evolution-3.44.2.tar.xz	12.5 MiB	2022-May-27 06:06

> Will send a screenshot and enquire on the Evo ML.
Please do. https://wiki.gnome.org/Apps/Evolution says:
"The evolution-list mailing list is the best place to seek further assistance with using Evolution, for example when you have problems
Subscribe here! [https://mail.gnome.org/mailman/listinfo/evolution-list]"

Your screenshot was useful. It shows HTML syntax, like viewing an HTML message as straight text; so it looks like Evolution is not recognising or treating it as an HTML message.

We should wait for an upstream response.

CC: (none) => lewyssmith
Keywords: (none) => UPSTREAM

Comment 3 aguador 2022-05-28 17:26:39 CEST

Upstream bug report: https://gitlab.gnome.org/GNOME/evolution/-/issues/1918

HTML messages generated by Evo itself can be responded to in plain text with no problem. However, HTML messages from other clients/editors are not.

Lewis Smith 2022-05-29 20:58:43 CEST

URL: (none) => https://gitlab.gnome.org/GNOME/evolution/-/issues/1918

Comment 4 Lewis Smith 2022-06-01 11:13:18 CEST

The upstream bug (worth a look) has been closed with a fix:
https://gitlab.gnome.org/GNOME/evolution/-/commit/51daf69dafd4726f996b34ceae1a31eee687790a

Note also that the maintainer advised equally to remove a previous patch:
https://gitlab.gnome.org/GNOME/evolution/-/commit/c7009fda1b891962e90768f2d8b003e004df4eac

Assigning to Olav who does most Evolution commits.

@aguador
If the correction makes it to core/updates_testing, please do test it. That would help a lot.

CC: lewyssmith => (none)
Assignee: bugsquad => olav
Summary: Evolution: responding to/forwarding HTML messages converts formatting commands to plain text => Evolution: responding to/forwarding HTML messages converts formatting commands to plain text. FIX AVAILABLE

Comment 5 aguador 2022-06-19 11:44:08 CEST

More than happy to test when it hits. I see that evo-server was rebuilt, but have not seen anything about evo itself. I've checked updates_testing from time to time. If it does hit there, a heads up would help as I will test ASAP.

Comment 6 aguador 2022-07-02 09:14:36 CEST

Update to 3.44.3 has solved the issue. Closing...

Status: NEW => RESOLVED
Resolution: (none) => FIXED