FS#25604 - [Evolution]3.0.2: quoted forwarding of e-mails not possible

Attached to Project: Arch Linux
Opened by Stefan Förster (HotblackDesiato) - Tuesday, 16 August 2011, 13:42 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 31 August 2011, 19:40 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No



Since Evolution 2.x I set the forwarding style to "quoted" instead of the default "attached". Under Evolution 3.0.2 I have the same setting "quoted", which can be found under "Options.../Editor Settings.../Reply and Forward/Quoted" (this might be slightly different in the original English version. In my German locale this reads as follows: "Einstellungen.../Editoreinstellungen.../Antworten und Weiterleitungen/Zitiert").

Additional info:
* package version(s): Evolution 3.0.2
* config and/or log files etc.

Steps to reproduce:
Install Evolution 3.0.2, set forwarding to "quoted" and forward an e-mail. It get's attached to the new e-mail, i.e. the setting "quoted" is ignored.
This task depends upon

Closed by  Ionut Biru (wonder)
Wednesday, 31 August 2011, 19:40 GMT
Reason for closing:  Fixed
Additional comments about closing:  evolution 3.0.3
Comment by Ionut Biru (wonder) - Tuesday, 16 August 2011, 13:48 GMT
please report this issue upstream to http://bugzilla.gnome.org. Don't forget to paste the link
Comment by Jan de Groot (JGC) - Monday, 29 August 2011, 16:42 GMT
Works fine here, Evolution 3.0.2. Maybe this is a settings migration issue, could you set it to something else, save the preference and then re-set it to quoted?
Comment by Stefan Förster (HotblackDesiato) - Monday, 29 August 2011, 19:26 GMT
That's what I tried first, but saving the preferences and then re-setting to "quoted" does not help.
Comment by Stefan Förster (HotblackDesiato) - Monday, 29 August 2011, 19:34 GMT
GNOME Bugzilla – Bug 657651 Submitted
Comment by Stefan Förster (HotblackDesiato) - Wednesday, 31 August 2011, 19:29 GMT
Today, I installed the update to version 3.0.3 and the bug is gone! Many thanks for your replies.