[rt-users] No Content from Replies for Requestors!

[Steve McStravick]

Here are the transactions from the DB.


37795	RT::Ticket	3144	0	Correspond	No Subject	1215
2011-02-02 20:22:44.0
37796	RT::Ticket	3144	0	EmailRecord
<rt-3.8.8-13428-1296678164-1466.3144-5-0 at eyelitrt>	1	2011-02-02
20:22:45.0
37797	RT::Ticket	3144	0	EmailRecord
<rt-3.8.8-13428-1296678165-1871.3144-23-0 at eyelitrt>	1	2011-02-02
20:22:46.0


And the attachments for these transactions:

12541	37795	0	rt-3.8.8-13428-1296678164-501.3144-0-0 at eyelitrt
multipart/mixed			"MIME-Version: 1.0
In-Reply-To: <rt-3.8.8-13636-1296677828-472.3144-0-0 at eyelitrt>
X-Mailer: MIME-tools 5.428 (Entity 5.428)
References: <RT-Ticket-3144 at eyelitrt>
 <9FF07362A2BFD446B95FC028D0B7B4D004F209C2 at companyx.net>
 <00cf01cbc30d$dc03d160$940b7420$@eyelit.com>
 <rt-3.8.8-13429-1296677577-59.3144-23-0 at eyelitrt>
 <9FF07362A2BFD446B95FC028D0B7B4D004F209C3 at companyx.net>
 <rt-3.8.8-13636-1296677828-472.3144-0-0 at eyelitrt>
Content-Type: multipart/mixed; boundary="----------=_1296678164-13428-5"
Message-ID: <rt-3.8.8-13428-1296678164-501.3144-0-0 at eyelitrt>
X-RT-Original-Encoding: utf-8
RT-Send-CC:
RT-Send-BCC:
Content-Length: 0
"	1215	2011-02-02 20:22:44.0
12542	37795	12541				text/html	none	{all
the binary crap}	"Content-Disposition: inline
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 184
"	1215	2011-02-02 20:22:44.0
12543	37795	12541		W_DC_MEASUREMENT_1.xml
W_DC_MEASUREMENT_1.xml	text/xml	none	{all the binary crap}
"MIME-Version: 1.0
Subject: W_DC_MEASUREMENT_1.xml
X-Mailer: MIME-tools 5.428 (Entity 5.428)
Content-Type: text/xml; name="W_DC_MEASUREMENT_1.xml"
Content-Disposition: inline; filename="W_DC_MEASUREMENT_1.xml"
Content-Transfer-Encoding: binary
Content-Length: 25099
"	1215	2011-02-02 20:22:44.0
12544	37796	0	rt-3.8.8-13428-1296678164-1466.3144-5-0 at eyelitrt
[RT #3144] Owner: (support_person) FW: Multi Sample DC 		text/plain
none	{all the binary crap}	"Subject: [RT #3144] Owner: (support_person)
FW: Multi Sample DC 
From: "SUPPORT PERSON via RT" <help at mycompany.com>
Reply-To: help at mycompany.com
In-Reply-To: <rt-3.8.8-13636-1296677828-472.3144-5-0 at eyelitrt>
References: <RT-Ticket-3144 at eyelitrt>
<9FF07362A2BFD446B95FC028D0B7B4D004F209C2 at companyx.net>
<00cf01cbc30d$dc03d160$940b7420$@eyelit.com>
<rt-3.8.8-13429-1296677577-59.3144-23-0 at eyelitrt>
<9FF07362A2BFD446B95FC028D0B7B4D004F209C3 at companyx.net>
<rt-3.8.8-13636-1296677828-472.3144-5-0 at eyelitrt>
Message-ID: <rt-3.8.8-13428-1296678164-1466.3144-5-0 at eyelitrt>
Precedence: bulk
X-RT-Loop-Prevention: mycompany.com
RT-Ticket: mycompany.com #3144
Managed-by: RT 3.8.8 (http://www.bestpractical.com/rt/)
RT-Originator: support_person at mycompany.com
Bcc: abunch_of_people at mycompany.com
MIME-Version: 1.0
X-RT-Original-Encoding: utf-8
Date: Wed, 2 Feb 2011 15:22:45 -0500
RT-Attachment: 3144/37795/12543
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
"	1	2011-02-02 20:22:45.0
12545	37797	0	rt-3.8.8-13428-1296678165-1871.3144-23-0 at eyelitrt
[RT #3144] FW: Multi Sample DC 		text/plain	none	{all the
binary crap}	"Sender: Support <help at mycompany.com> 
From: Eyelit Support <help at mycompany.com>
Subject: [RT #3144] FW: Multi Sample DC 
Reply-To: help at mycompany.com
In-Reply-To: <rt-3.8.8-13636-1296677828-472.3144-23-0 at eyelitrt>
References: <RT-Ticket-3144 at eyelitrt>
<9FF07362A2BFD446B95FC028D0B7B4D004F209C2 at companyx.net>
<00cf01cbc30d$dc03d160$940b7420$@eyelit.com>
<rt-3.8.8-13429-1296677577-59.3144-23-0 at eyelitrt>
<9FF07362A2BFD446B95FC028D0B7B4D004F209C3 at companyx.net>
<rt-3.8.8-13636-1296677828-472.3144-23-0 at eyelitrt>
Message-ID: <rt-3.8.8-13428-1296678165-1871.3144-23-0 at eyelitrt>
Precedence: bulk
X-RT-Loop-Prevention: mycompany.com
RT-Ticket: mycompany.com #3144
Managed-by: RT 3.8.8 (http://www.bestpractical.com/rt/)
RT-Originator: support_person at mycompany.com
To: my_customer at email.com
MIME-Version: 1.0
X-RT-Original-Encoding: utf-8
Date: Wed, 2 Feb 2011 15:22:45 -0500
RT-Attachment: 3144/37795/12542
RT-Attachment: 3144/37795/12543
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
"	1	2011-02-02 20:22:46.0


Message: 2
Date: Fri, 04 Feb 2011 10:17:03 -0500
From: Thomas Sibley <trs at bestpractical.com>
To: RT Users <rt-users at lists.bestpractical.com>
Subject: Re: [rt-users] No Content from Replies for Requestors!
Message-ID: <4D4C186F.4020707 at bestpractical.com>
Content-Type: text/plain; charset=UTF-8

On 04 Feb 2011 10:02, Steve McStravick wrote:
> We are rolling out RT 3.8.8 and have hit the following issues a couple
> of times now, but not always!
> 
> Replies Sent out to our Requestors and Cc  sometime show ?Transaction
> contains no content? when there IS content,

It might be helpful here to see the original transactions and
attachments, pulled from the database.

Are the times you get "Transaction contains no content" generated from
email or web correspondence?

Thomas