[rt-users] [rt-announce] Development Snapshot 3.0.2++
Dirk Pape
pape-rt at inf.fu-berlin.de
Mon May 26 12:41:38 EDT 2003
Hello Jesse,
--Am Freitag, 23. Mai 2003 16:24 Uhr -0400 schrieb Jesse Vincent
<jesse at bestpractical.com>:
> This isn't a formal pre-release of RT 3.0.3, but a snapshot that fixes
> some of the utf8 issues in RT 3.0.2 that have been biting
> western-european users. If you don't have utf8-issues that you need to
> deal with ASAP, hold off a bit.
>
I have still the same issues as decribed earlier and I can now fuzzily
reproduce them (see below)
>From an earlier posting of mine:
> So I start with my config:
>
> RT: Version 3.0.2++
> OS: Debian Linux Woody
> Apache: 1.3.26 with SSL
> Modperl: 1
> DBS. mysql 3.23
> Perl: 5.8.0
> sbin/rt-testdepedencies happy with all installed perl-libs
>
> my issues (please add your's and your comments):
>
> 2. from time to time incoming (non-utf8) Email will not be converted any
> more to utf8. It will though be marked as being converted, but in real
> contain ISO-character-encodings. I have to be vague here, because I
> cannot reproduce any trigger of this behaviour. But if this happens, it
> seems to stick for one apache process.
httpd.conf:
...
SSLEnable
AddDefaultCharset UTF-8
<Location /rt>
order allow,deny
allow from all
PerlRequire /export/rt3/bin/webmux.pl
SetHandler perl-script
PerlHandler RT::Mason
...
</Location>
RT_Siteconfig:
...
@EmailInputEncodings = qw(utf-8 iso-8859-1 us-ascii) unless
(@EmailInputEncodings);
Set($EmailOutputEncoding , 'iso-8859-15');
...
REPRODUCTION OF PROBLEM:
I attach a digest with mails I send one after another to the rt-system and
they get queued into one queue, each as a new ticket.
The first two tickets are displayed correctly.
After the third or fourth ticket arrived, the subject field in the web
display (ticket history is garbled and shows "Subject: test
�ö������� " (The concrete garbage depend on the browser you use
to display.
BUT: If you go to the "The Basics" panel, the subject shows ok. So does the
subject of the Auto-Reply the user receives per Email.
If I do further send the same message (I sometimes varied the number of
line breaks at the end of the message), I arrive to different states, in
arbitrary order:
A) Some of the messages arrive intact
B) Some of the messages have garbled subjects
C) Some of the messages have garbled bodies (This then also applies to the
autoreplies which cite the body by including Transaction->Content into the
message.
I even observed the case that there was an alternation (Ticket 2n =>
garbled Subject, Ticket 2n+1 => garbled body)
So you might be able to reprduce the thing at your site.
If not I will be glad to provide you with further infos you need (queue
config, scrips a.s.o)
Regards,
Dirk.
More information about the rt-users
mailing list