Le 20/09/2013 à 08:58:35+0400, Ruslan Zakirov a écrit Hi, > > You didn't say how to reproduce the problem. Should it be email? Should it be > UI?
Only from email. When I send a email with some utf-8 character inside the subject the problem appear. I try to track the problem, so I installe a new server (FreeBSD), dump the all mysql base and rt config, put inside the new server and the problem still here. I disable all plugin and enable debug mode in RT : Here the log I find (It's really at the beginning : ) Sep 20 20:53:37 support-new RT: Converting 'iso-8859-1' to 'utf-8' for text/plain - Essai é, è, ã Sep 20 20:53:37 support-new RT: Mail from user #22 ([email protected]) Sep 20 20:53:37 support-new RT: About to think about scrips for transaction #203642 Sep 20 20:53:37 support-new RT: About to think about scrips for transaction #203643 Sep 20 20:53:37 support-new RT: About to think about scrips for transaction #203644 Sep 20 20:53:37 support-new RT: About to think about scrips for transaction #203645 Sep 20 20:53:37 support-new RT: About to think about scrips for transaction #203646 Sep 20 20:53:37 support-new RT: About to prepare scrips for transaction #203646 Sep 20 20:53:37 support-new RT: Found 3 scrips for TransactionCreate stage with applicable type(s) Create for txn #203646 on ticket #10767 Sep 20 20:53:37 support-new RT: Converting 'utf-8' to 'utf-8' for text/plain - =?UTF-8?B?W0luZm8gT2JzcG0gIzEwNzY3XSBFc3NhaSDvv70sIO+/vSwg77+9?= Sep 20 20:53:37 support-new RT: Converting 'utf-8' to 'utf-8' for text/plain - =?UTF-8?B?W0luZm8gT2JzcG0gIzEwNzY3XSBFc3NhaSDvv70sIO+/vSwg77+9?= at this point something is wrong because echo "W0luZm8gT2JzcG0gIzEwNzY3XSBFc3NhaSDvv70sIO+/vSwg77+9" |base64 -d [Info Obspm #10767] Essai �, �, � and missing a "\n" at the end It should be something like : echo "[Info Obspm #10767] Essai é, è, ã" |base64 W0luZm8gT2JzcG0gIzEwNzY3XSBFc3NhaSDDqSwgw6gsIMOjCg== More stranger, if now I close the ticket from the web UI the mail RT send to me is correct. Thank you very much for you help. > > Hi, > > > > I just upgrade to rt 4.0.17 under freebsd. > > > > After the upgrade we got a big problem with encoding subject. > > > > If the subject is detected as utf-8 RT re-encode so a subject like > > > > Essai é > > > > is encode like > > > > Subject: =?UTF-8?B?W21hdGguY25ycy5mciAjMzM3OV0gRXNzYWkgw6k=?= > > > > but since my upgrade the encoding is wrong. > > > > Subject: =?UTF-8?B?W0luZm8gT2JzcG0gIzEwNzMxXSBFc3NhaSDvv70=?= > > > > And the problem become very big is with some subjet (always UTF-8) the > > scrip don't work anymore. > > > > If I send a message with > > > > Essai é à ẽ ã > > > > as a subject, RT don't send any mail to admin. > > > > Any idea ? > > I check the log, and found this message > > RT: Malformed UTF-8 character (unexpected end of string) in string ne at / > usr/local/lib/perl5/site_perl/5.16/Locale/Maketext.pm line 538. > (/usr/local > /lib/perl5/site_perl/5.16/Locale/Maketext.pm:538) > RT: Malformed UTF-8 character (unexpected end of string) in string ne at / > usr/local/lib/perl5/site_perl/5.16/Locale/Maketext.pm line 538. > (/usr/local > /lib/perl5/site_perl/5.16/Locale/Maketext.pm:538) > > > not sure it's related but I guess it'is. > > So I installed old version of > > p5-Locale-Maketext-Lexicon > > but nothing change. > > I also try with > > p5-Encode > > but no chance either. > > Can someone tell me which perl package is used by RT to « encode » subject > ? So I can check if the problem come from RT 4.0.17 or some new perl > packages. > Bests regards. JAS -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex France Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71 xmpp: [email protected] Heure local/Local time: ven 20 sep 2013 22:49:40 CEST -- RT Training in New York, October 8th and 9th: http://bestpractical.com/training
