Main encoding problem

Hi,

I have a persistent problem with mangled messages. I think the same
problem affects both message text and attachments. A message enters
the system using one charset, but it seems RT (in a wide sense) gets
it wrong.

Here are the incoming raw message headers:

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Note in particular the Content-Type line. Here is the message the is
sent out by RT:

Managed-BY: RT 3.0.10 (http://www.bestpractical.com/rt/)
MIME-Version: 1.0
In-Reply-To: rt-692@Dynasim
RT-Ticket: Dynasim #692
Message-Id: rt-3.0.10-692-3918.1.06322901111625@dynasim.se
Precedence: bulk
Content-Type: text/plain; charset="iso-8859-1"
BCC:
X-RT-Original-Encoding: utf-8

What strikes me as particularly odd is the X-RT-Original-Encoding. The
text is also mangled, at least “funny” natinal characters outside of
ASCII.

Here is some system information:

RT: 3.0.10
Perl: 5.8.3
mod_perl: 1.27 (reinstalled after upgrading to Perl 5.8.3
Apache: 1.3.27 (not recompiled after upgrading to Perl 5.8.3)
Linux: RedHat 7.2

All Perl modules meet the requirements for RT 3.0.10, but I’m not sure
they are the latest thing. Neither have I downloaded them after the
latest Perl upgrade (we used to run 5.8.0 before).

Also of interest might be that I have set RT’s output encoding to
iso-8859-1. We have some mail programs that do not like UTF-8 very
much. From RT_SiteConfig.pm:

@EmailInputEncodings = qw(utf-8 iso-8859-1 us-ascii) unless (@EmailInputEncodings);
#Set($EmailOutputEncoding , ‘utf-8’);
Set($EmailOutputEncoding , ‘iso-8859-1’);

Any help would be GREATLY apprciated! I have run UNIX systems for
quite some time, but Perl administration is pretty new to me.

Best regards,

Dag Bruck
Dynasim, Lund, Sweden

I found the following information regarding a Perl bug (still present
in the latest development version of Perl, 5.9.1). Do we have a fix
that does not involve modifying Perl source now?

Best regards,

Dag Br�ck
Dynasim, Sweden

Author: Jesse VincentDate: 2004-01-07 19:18 +100
To: rt-devel, rt-users
Subject: [rt-users] Re: Solution to corrupt attachments problem with RT3 and perl

Nicholas has tracked the intermittent bug that causes attachment
corruption for some users to a bug in perl’s “join” method. There is a
potential fix that doesn’t involve directly modifying perl’s source code,
but we don’t have that available just yet.

Yes, it’s called 5.8.3On Tue, Mar 30, 2004 at 05:13:15PM +0200, Dag Bruck wrote:

I found the following information regarding a Perl bug (still present
in the latest development version of Perl, 5.9.1). Do we have a fix
that does not involve modifying Perl source now?

Best regards,

Dag Br�ck
Dynasim, Sweden


Author: Jesse Vincent
Date: 2004-01-07 19:18 +100
To: rt-devel, rt-users
Subject: [rt-users] Re: Solution to corrupt attachments problem with RT3 and perl

Nicholas has tracked the intermittent bug that causes attachment
corruption for some users to a bug in perl’s “join” method. There is a
potential fix that doesn’t involve directly modifying perl’s source code,
but we don’t have that available just yet.


rt-users mailing list
rt-users@lists.bestpractical.com
The rt-users Archives

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.

Jesse Vincent jesse@bestpractical.com writes:

Yes, it’s called 5.8.3

Ok, but my original mails says I’m running Perl 5.8.3.
Can anyone please give me a hint what I should do.

For example, what is the safest way to get a clean install
of Perl 5.8.3 without traces of 5.8.0?

Dag