[rt-users] Character sets and broken attachments (Was: Broken UTF8 putting down Quoted.pm when displaying a ticket?)

[Simo Melenius]

A week ago, I, Simo Melenius wrote:

> I'm getting a similar error as in 
> <URL:http://lists.fsck.com/pipermail/rt-users/2003-October/017188.html>: 
> Quoted.pm killing itself because of invalid UTF8. Google didn't find any 
> Text::Quoted: 1.2

I found the answer myself, thanks to him who also hinted towards 
Text::Quoted 1.3 anyway. Here's another question:



Now that I've been playing with RT3.0.6 for about a week, I've noticed a 
lot of problems with corrupt attachments. Tuning the preferred character 
sets for Encode::Guess (EmailInputEncodings and EmailOutputEncoding) to 
not include utf-8 helps a bit, but there still seems to be occasional 
problems with mistaken UTF8 and 1:1-octet-based character sets (like 
latin1).

The text parts of the messages show up OK, but attachment data sometimes 
seems to get high-characters converted to UTF8, eventhough the binary 
attachment is base64-encoded in the mime message. This is for incoming 
email messages; also, uploading files from RT using the webform 
sometimes corrupts the binary attachment, but of course, not always. I 
even rudely set Encode::Guess::NoUTFAutoGuess to 1 but it hasn't helped. 
For example, I tested uploading a file with Mozilla and it went there 
OK, but a colleague tried with IE5.5 and it got utf-8ized.


Is there a known problem regarding this? If not, I can provide more 
information on this.


br:s

-- 
simo.melenius at citec.fi         System Designer / Unix Applications
Tel: +358 50 347 8373                  CiTEC Information Solutions