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@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@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@eyelitrt
multipart/mixed "MIME-Version: 1.0
In-Reply-To: <rt-3.8.8-13636-1296677828-472.3144-0-0@eyelitrt>
X-Mailer: MIME-tools 5.428 (Entity 5.428)
References: <RT-Ticket-3144@eyelitrt>
<9ff07362a2bfd446b95fc028d0b7b4d004f20...@companyx.net>
<00cf01cbc30d$dc03d160$940b7420$@eyelit.com>
<rt-3.8.8-13429-1296677577-59.3144-23-0@eyelitrt>
<9ff07362a2bfd446b95fc028d0b7b4d004f20...@companyx.net>
<rt-3.8.8-13636-1296677828-472.3144-0-0@eyelitrt>
Content-Type: multipart/mixed; boundary="----------=_1296678164-13428-5"
Message-ID: <rt-3.8.8-13428-1296678164-501.3144-0-0@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@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" <h...@mycompany.com>
Reply-To: h...@mycompany.com
In-Reply-To: <rt-3.8.8-13636-1296677828-472.3144-5-0@eyelitrt>
References: <RT-Ticket-3144@eyelitrt>
<9ff07362a2bfd446b95fc028d0b7b4d004f20...@companyx.net>
<00cf01cbc30d$dc03d160$940b7420$@eyelit.com>
<rt-3.8.8-13429-1296677577-59.3144-23-0@eyelitrt>
<9ff07362a2bfd446b95fc028d0b7b4d004f20...@companyx.net>
<rt-3.8.8-13636-1296677828-472.3144-5-0@eyelitrt>
Message-ID: <rt-3.8.8-13428-1296678164-1466.3144-5-0@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_per...@mycompany.com
Bcc: abunch_of_peo...@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@eyelitrt
[RT #3144] FW: Multi Sample DC text/plain none {all the
binary crap} "Sender: Support <h...@mycompany.com>
From: Eyelit Support <h...@mycompany.com>
Subject: [RT #3144] FW: Multi Sample DC
Reply-To: h...@mycompany.com
In-Reply-To: <rt-3.8.8-13636-1296677828-472.3144-23-0@eyelitrt>
References: <RT-Ticket-3144@eyelitrt>
<9ff07362a2bfd446b95fc028d0b7b4d004f20...@companyx.net>
<00cf01cbc30d$dc03d160$940b7420$@eyelit.com>
<rt-3.8.8-13429-1296677577-59.3144-23-0@eyelitrt>
<9ff07362a2bfd446b95fc028d0b7b4d004f20...@companyx.net>
<rt-3.8.8-13636-1296677828-472.3144-23-0@eyelitrt>
Message-ID: <rt-3.8.8-13428-1296678165-1871.3144-23-0@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_per...@mycompany.com
To: my_custo...@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 <t...@bestpractical.com>
To: RT Users <rt-users@lists.bestpractical.com>
Subject: Re: [rt-users] No Content from Replies for Requestors!
Message-ID: <4d4c186f.4020...@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
