Bug 209895

Summary:	'Forward Inline' does not include the forwarded message inline
Product:	[Unmaintained] kmail	Reporter:	Maurice Batey <maurice>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bjoern, maurice
Priority:	NOR
Version:	1.11.4
Target Milestone:	---
Platform:	Mandriva RPMs
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Maurice Batey 2009-10-08 19:11:10 UTC

Version:           1.11.4 (using KDE 4.2.4)
OS:                Linux
Installed from:    Mandriva RPMs

When wishing to Forward the current message, selecting the 'Inline' option results in a composed *empty* message, instead of containing the text of the message to be forwarded. (And if sent, the recipient receives an empty message.)

(No problem  if 'Attached' is selected instead of 'Inline'.)

Comment 1 Maurice Batey 2009-10-13 18:40:44 UTC

Please note I shall be away until November 3rd.

Comment 2 Jaime Torres 2009-10-14 09:42:11 UTC

In the inline mode, where you can see the message that will be sent, if the message is empty, means that the template for forward inline is empty.
Please check the folder templates, the account templates and the global templates.

Comment 3 Maurice Batey 2009-10-14 13:08:05 UTC

You are right - the template does not contain "%TEXT".

But WHY NOT? What is the point of selecting 'Forward Inline' if the default action is an empty message?

The default setting for 'Forward' in KMail 1.9.10 (KDE 3.5.10) on Mandriva 2009.0 is:

%REM="Default forward template"%-

----------  Forwarded Message  ----------

Subject: %OFULLSUBJECT
Date: %ODATE
From: %OFROMADDR
To: %OTOADDR

%TEXT
-------------------------------------------------------

I suggest the latest default should be the same/similar.

Comment 4 Björn Ruberg 2010-03-06 15:39:01 UTC

The forwarding template does contain this by default - but it can happen that your templates are deleted. Happend once to me. I think that is your real problem. That's why I'm marking this as a duplicate of the corresponding bug.

*** This bug has been marked as a duplicate of bug 184307 ***