RT fooled by "headers" in body

If I were to write a mail with the following content in the BODY of an email message
and send to an RT address, RT does 2 things incorrectly.

  1. Mails to AdminCCs appears to come from abc@abc.com to efg@efg.com with subject “Mysubject”. (instead of from “sender via RT” and to “admincc of xxx”)

  2. An outgoing mail goes to efg@efg.com (not an autoreply)

Message in body:
-----8<------------
X-Mailer: Mozilla 4.77 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

blah blah blah
-----8<-------------

Apparently, think RT has been fooled by the “header” lines in the email body.
RT should really treat stuff after a new line as pure message of a body.

I’m using 2.0.5_03.
Yeow

That sounds like you’ve set up a custom template containing only
the following line

<%$Transaction->Content%>

or something like it. RT would interpret your transaction’s content as
the whole of the template, including using its header as the mail message’s
header.

Is what’s stored in RT ‘correct’ or does it look like the mail messages
that are being sent out?On Wed, Aug 22, 2001 at 01:56:17PM +0800, Yeow wrote:

If I were to write a mail with the following content in the BODY of an email message
and send to an RT address, RT does 2 things incorrectly.

  1. Mails to AdminCCs appears to come from abc@abc.com to efg@efg.com with subject “Mysubject”. (instead of from “sender via RT” and to “admincc of xxx”)

  2. An outgoing mail goes to efg@efg.com (not an autoreply)

Message in body:
-----8<------------
Date: Fri, 17 Aug 2001 03:10:43 +0800
From: abc abc@abc.com
X-Mailer: Mozilla 4.77 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: efg@efg.com
Subject: Mysubject
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

blah blah blah
-----8<-------------

Apparently, think RT has been fooled by the “header” lines in the email body.
RT should really treat stuff after a new line as pure message of a body.

I’m using 2.0.5_03.
Yeow

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

I’m using the global correspondence template with the following code:
{
$Transaction->Attachments(‘text/plain’)->First->Content ||
$Transaction->Attachments(‘text/html’)->First->Content ||
“No Viewable Message.”
}
This works best for me because most of mails I get are multipart text+html
messages.
( till RT can forward mails “as is” :slight_smile: )

RT stores the mails correctly. The “header” lines in the body are correctly
intepretted as text.
But mails sent out does not have the extra header lines as text.

Following your clue, I introduced a new line(in fact any character) before
the code in the template and everything works fine now.

So now I see that the template is indeed powerful. Thanks for the help.

YeowFrom: “Jesse Vincent” jesse@bestpractical.com
To: “Yeow” yeowhui@i-dns.net
Cc: “rt-users” rt-users@lists.fsck.com
Sent: Wednesday, August 22, 2001 2:20 PM
Subject: Re: [rt-users] RT fooled by “headers” in body

That sounds like you’ve set up a custom template containing only
the following line

<%$Transaction->Content%>

or something like it. RT would interpret your transaction’s content as
the whole of the template, including using its header as the mail
message’s
header.

Is what’s stored in RT ‘correct’ or does it look like the mail messages
that are being sent out?