UTF-16 problem

RT Users
1

Hello all,

We are in the proces of rolling out a new installation of RT 4.0.5.

Everything has been setup using the documents. Now we face a problem when someone e-mails us an attachment with UTF-16. In the logs we can see:

RT server error.

The RT server which handled your email did not behave as expected. It
said:

UTF-16:Unrecognised BOM 7465 at /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/Encode.pm line 196.

Stack:
[/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/Encode.pm:196]
[/opt/rt4/sbin/…/lib/RT/I18N.pm:549]
[/opt/rt4/sbin/…/lib/RT/I18N.pm:214]
[/opt/rt4/sbin/…/lib/RT/I18N.pm:210]
[/opt/rt4/sbin/…/lib/RT/EmailParser.pm:282]
[/opt/rt4/sbin/…/lib/RT/Interface/Email.pm:1399]
[/opt/rt4/share/html/REST/1.0/NoAuth/mail-gateway:61]

When we login to the mailbox, we can see in the full headers it is an UTF-16 attachment:

--------------000705080004050904010106
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

--------------000705080004050904010106
Content-Type: text/plain; charset=UTF-16;

name="attachment.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename=“attachment.txt”
--------------000705080004050904010106–

Server is a RHEL5, perl 5.8.8. We use fetchmail which calls RT-mailgate to fill the queues. We have tried several EmailInputEncodings but no success there. Any clues?

Regards,

Dennis

2

Hi,

Can you send archived email in MIME format, so we can try to reproduce
the problem?

Value of EmailInputEncodings options would be helpful as well.On Mon, Mar 5, 2012 at 16:38, Dennis dennis_20@yahoo.com wrote:

Hello all,

We are in the proces of rolling out a new installation of RT 4.0.5.

Everything has been setup using the documents. Now we face a problem when someone e-mails us an attachment with UTF-16. In the logs we can see:

RT server error.

The RT server which handled your email did not behave as expected. It
said:

UTF-16:Unrecognised BOM 7465 at /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/Encode.pm line 196.

Stack:
[/usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/Encode.pm:196]
[/opt/rt4/sbin/…/lib/RT/I18N.pm:549]
[/opt/rt4/sbin/…/lib/RT/I18N.pm:214]
[/opt/rt4/sbin/…/lib/RT/I18N.pm:210]
[/opt/rt4/sbin/…/lib/RT/EmailParser.pm:282]
[/opt/rt4/sbin/…/lib/RT/Interface/Email.pm:1399]
[/opt/rt4/share/html/REST/1.0/NoAuth/mail-gateway:61]

When we login to the mailbox, we can see in the full headers it is an UTF-16 attachment:

--------------000705080004050904010106
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

--------------000705080004050904010106
Content-Type: text/plain; charset=UTF-16;

name=“attachment.txt”
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename=“attachment.txt”
--------------000705080004050904010106–

Server is a RHEL5, perl 5.8.8. We use fetchmail which calls RT-mailgate to fill the queues. We have tried several EmailInputEncodings but no success there. Any clues?

Regards,

Dennis

RT Training Sessions (http://bestpractical.com/services/training.html)

  • Boston March 5 & 6, 2012

Best regards, Ruslan.