Hello all,
We’re observing a problem with incoming e-mails where the message body
is
empty after getting piped into RT. The only difference between the
e-mails
that fail and the ones that succeed is the following header exists on
the
failed transactions:
Content-Type: text/plain; charset=“utf-8”
and the following exists on the successful transactions:
Content-Type: text/plain; charset=“us-ascii”
Should we be filtering the messages with something before handing it off
to
RT or is RT capable of handling “utf-8” encoded messages and something
else is probably amiss?
Any help would be greatly appreciated.
Thanks,
Chris
StillSecure
Christopher Fernando
Security Engineer
303-381-3802 Support
303-381-3880 Fax
www.stillsecure.com
The information transmitted is intended only for the person to whom it
is addressed and may contain confidential material. Review or other use
of this information by persons other than the intended recipient is
prohibited. If you’ve received this in error, please contact the sender
and delete from any computer.
Hello all,
We’re observing a problem with incoming e-mails where the message body > is
empty after getting piped into RT. The only difference between the > e-mails
that fail and the ones that succeed is the following header exists on > the
failed transactions:
Content-Type: text/plain; charset=“utf-8”
and the following exists on the successful transactions:
Content-Type: text/plain; charset=“us-ascii”
Should we be filtering the messages with something before handing it off > to
RT or is RT capable of handling “utf-8” encoded messages and something
else is probably amiss?
RT certainly should be handling utf8 content just fine. Can you try
reporting the bug as a utf8 message to rt-bugs@fsck.com?
We’ll see if our RT handles it ok.
Further research shows that the integer value of the special character
in the e-email that is causing the transaction to have no data is
“12244”. This looks like a Chinese character…
Any reason why this Unicode character would cause the entire message
body to be discarded by RT?
StillSecure
Christopher Fernando
Security Engineer
303-381-3802 Support
303-381-3880 Fax
www.stillsecure.com
The information transmitted is intended only for the person to whom it
is addressed and may contain confidential material. Review or other use
of this information by persons other than the intended recipient is
prohibited. If you’ve received this in error, please contact the sender
and delete from any computer.From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: Monday, August 14, 2006 1:00 PM
To: Chris Fernando
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] v3.6.0 empty transaction with utf-8 content-type
Hello all,
We’re observing a problem with incoming e-mails where the message body
is
empty after getting piped into RT. The only difference between the >
e-mails
that fail and the ones that succeed is the following header exists on
the
failed transactions:
Content-Type: text/plain; charset=“utf-8”
and the following exists on the successful transactions:
Content-Type: text/plain; charset=“us-ascii”
Should we be filtering the messages with something before handing it
off > to
RT or is RT capable of handling “utf-8” encoded messages and something
else is probably amiss?
RT certainly should be handling utf8 content just fine. Can you try
reporting the bug as a utf8 message to rt-bugs@fsck.com?
We’ll see if our RT handles it ok.
Any help would be greatly appreciated.
Thanks,
Chris
–
StillSecure
Christopher Fernando
Security Engineer
303-381-3802 Support
303-381-3880 Fax
www.stillsecure.com
The information transmitted is intended only for the person to whom it
is addressed and may contain confidential material. Review or other
use
of this information by persons other than the intended recipient is
prohibited. If you’ve received this in error, please contact the
sender
and delete from any computer.
The rt-users Archives
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com