OK,
I’m having trouble with outbound correspondences from RT not including
attachments. The correspondence in the web interface shows:
Tue Oct 13 12:36:59 2009
acoco - Correspondence added
[Reply
<http://rt.i2c.com/Ticket/Update.html?id=4911&QuoteTransaction=6620&Acti
on=Respond> ] [Comment
<http://rt.i2c.com/Ticket/Update.html?id=4911&QuoteTransaction=6620&Acti
on=Comment> ]
Download (untitled) http://rt.i2c.com/Ticket/Attachment/6620/4092/
[text/plain 270b]
new attachment. server restart. DB longblob fix. work?
maybe this time with overlay hack?
Install Encode::Guess fix?
Download Attach this.txt
http://rt.i2c.com/Ticket/Attachment/6620/4095/Attach%20this.txt
[text/plain 20b]
Does this need data?
But the Outgoing email record shows:Subject: [Support #4911] attachment test
From: “Partner Diligence Support” pdsupport@partnerdiligence.com
Reply-To: rt@i2c.com
In-Reply-To: rt-3.6.7-29475-1255446425-1580.4911-6-0@rt.i2c.com
References: RT-Ticket-4911@rt.i2c.com
976eb4120910130601k2084e41aw447b88414e8a07f3@mail.gmail.com
rt-3.6.7-5274-1255443088-1726.4911-6-0@rt.i2c.com
rt-3.6.7-29768-1255445623-299.4911-6-0@rt.i2c.com
rt-3.6.7-29475-1255446425-1580.4911-6-0@rt.i2c.com
Message-ID: rt-3.6.7-8071-1255451819-505.4911-6-0@rt.i2c.com
Precedence: bulk
X-RT-Loop-Prevention: Support
RT-Ticket: Support #4911
Managed-by: RT 3.6.7 (Request Tracker... So much more than a help desk — Best Practical Solutions)
RT-Originator: acoco@i2c.com
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=“utf-8”
X-RT-Original-Encoding: utf-8
Date: Tue, 13 Oct 2009 12:37:00 -0400
new attachment. server restart. DB longblob fix. work?
maybe this time with overlay hack?
Install Encode::Guess fix?
In googling the problem it was suggested that changing the Content
column of the Attachments table from longtext to longblob would correct
the problem, which I did. I also reinstalled the perl module ‘Encode’
as there were errors regarding that module in the log. I also read a
previous post suggesting a patch to Attachment_Overlay.pm and Web.pm,
however on inspection of those files it appears the code was already
patched. Has anyone else encountered this problem with RT3.6, on Debian
5.0.3, apache 2.2.9, perl 5.10.0.
Any advice greatly appreciated.
-alex