Problems with MIME-encodings in the Subject


#1

Hi!

We’re using request tracker for one week now and we’re really happy with
this great tool! Thanks to all who work on this project! (It’s sad to
hear that the development will probably be split up…)

One problem we currently have: If the Subject: line of an email targetted
to RT contains non-standard characters (German umlauts in our case), these
lines are encoded by the email client of the sender and with that RT
doesn’t recognize the email as reply to an existing request and opens a
new request. The second problem is that such requests are displayed with
an unreadable subject in the queue list, for example

           =?iso-8859-1?Q?ler_beim_Ausf=FChren_des_CGI-Scripts!!!?=

Does someone have a patch or know a work-around to make RT handle MIME
encoded Subject-lines correctly?

Thanks in advance,

Chris

, Christian Schwarz
/ o _
schwarz@schwarz-online.com, schwarz@monet.m.isar.de
! ; C.Schwarz@schwarz-consulting.de, chris@zwart.de
\ /
\_
__/ ! PGP-fp: 8F 61 EB 6D CF 23 CA D7 34 05 14 5C C8 DC 22 BA
\ / http://schwarz-online.com
-.-.,—,-,-…—,-,-.,----.-.-
“DIE ENTE BLEIBT DRAUSSEN!”