Email messages converted to UTF-8 twice

RT Users
1

Hi!

I have problems with RT, also reported by other users the last couple of
days. When emailing, all text in the mail (usually email in iso-8859-1) is
converted to UTF-8 twice before being stored in the attachments table’s
`content’ field. The subject field is correct, by the way.

I run FreeBSD-4.9, apache 1.3.29, RT-3.0.8.

Has this something to do with the perl bug reported a week ago?

I attach a text file (8859-1 encoded and gzipped). In it are two examples.
The first fails and is converted twice. The second actually get correctly
into the database, but then the header cannot be parsed (seems perl makes a
bad assumption about the character set beeing ascii?) so it cannot send any
autoreply instead.

Any help appreciated.

/Palle

foo.txt.gz (3.08 KB)

2

Hi!

I attach a text file (8859-1 encoded and gzipped). In it are two examples.
The first fails and is converted twice. The second actually get correctly
into the database, but then the header cannot be parsed (seems perl makes a
bad assumption about the character set beeing ascii?) so it cannot send any
autoreply instead.

Any help appreciated.

Thanks to everyone who’s reported examples of the issue that’s not
related to the IO::Stringy fix. I’m travelling this week, but you can
rest assured that I’ll dig into it when I’m back at my desk next week.

As an aide, the fix to join() that our custom IO::Stringy works around
was added to perl 5.8.3, which should be announced within next several
days, but is already available from Perl Source - www.cpan.org

Best,
Jesse
(From a cafe in Madrid)

/Palle

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... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

3

As an aide, the fix to join() that our custom IO::Stringy works around
was added to perl 5.8.3, which should be announced within next several
days, but is already available from Perl Source - www.cpan.org

Hello all,

I have recompiled perl 5.8.3 for debian testing yesterday and for now it
seems that it fixed double encoding problem.

So I encourage anybody to try perl 5.8.3 if they have problem with
double utf-8 encoded emails.

Best regards,
Ondřej Surý sury.ondrej@globe.cz
Globe Internet s.r.o.

4

Hi!

I have problems with RT, also reported by other users the last couple of
days. When emailing, all text in the mail (usually email in iso-8859-1) is
converted to UTF-8 twice before being stored in the attachments table’s
`content’ field. The subject field is correct, by the way.

I’ve heard reports that perl 5.8.3 fixes this issue. I’d love to hear
either way.

Jesse

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

5

Hello Jesse,

–Am Montag, 19. Januar 2004 11:43 Uhr -0500 schrieb Jesse Vincent
jesse@bestpractical.com:

I’ve heard reports that perl 5.8.3 fixes this issue. I’d love to hear
either way.

I have upgraded from perl 5.8.2 to 5.8.3 three days ago and I have not seen
any double encodings since then. Normally there were several a day. So I am
quite confident, that the issue (for us here) is fixed with 5.8.3.

I will cry loud enough, if it turns out that I am wrong :wink:

Thanks,
Dirk.

6

“Jesse” == Jesse Vincent jesse@bestpractical.com writes:

I’ve heard reports that perl 5.8.3 fixes this issue. I’d love to
hear either way.

This has also fixed mine. Great!

Sam
Samuel Tardieu – sam@rfc1149.net – About me

7

Hi,

I can confirm that all my troubles with double utf conversion have
disappeared when I updated perl from 5.8.2 → 5.8.3.

/Palle–On måndag, januari 19, 2004 11.43.15 -0500 Jesse Vincent jesse@bestpractical.com wrote:

On Thu, Jan 15, 2004 at 02:20:10AM +0100, Palle Girgensohn wrote:

Hi!

I have problems with RT, also reported by other users the last couple of
days. When emailing, all text in the mail (usually email in iso-8859-1)
is converted to UTF-8 twice before being stored in the attachments
table’s `content’ field. The subject field is correct, by the way.

I’ve heard reports that perl 5.8.3 fixes this issue. I’d love to hear
either way.

Jesse

–
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.