On Fri, Oct 12, 2012 at 1:24 PM, Xavier Reigner <[email protected]> wrote: > Alex your guess was correct. The messages are now correctly imported. I > prefer this to the binary file. > Thanks a lot, > X
Software that sends email is incorrect and should use the following Oracle function to convert charset name to valid name for emails. http://docs.oracle.com/cd/E11882_01/appdev.112/e16760/u_i18n.htm#i1001102 Information just in case you control sender. > On 12 October 2012 11:09, Alex Vandiver <[email protected]> wrote: >> >> On Fri, 2012-10-12 at 10:52 +0200, Xavier Reigner wrote: >> > It's better as the emails are not hanging in the mail box, but it >> > still not the perfect solution as the content needs more time to be >> > read. >> > What is missing ? >> >> "we8iso8859p1" appears to be an Oracle-only way of saying "iso-8859-1". >> I suspect that telling RT that those are equivalent is all that is >> necessary. You can do that by adding the following to your >> RT_SiteConfig.pm: >> >> require Encode::Alias; >> Encode::Alias::define_alias("we8iso8859p1" => "iso-8859-1"); >> >> You may also want to look into the software that is generating the mail >> in question, and see if it can be altered to provide the standard name >> for the character set. >> - Alex >> >> >> -------- >> Final RT training for 2012 in Atlanta, GA - October 23 & 24 >> http://bestpractical.com/training >> >> We're hiring! http://bestpractical.com/jobs > > > > > -------- > Final RT training for 2012 in Atlanta, GA - October 23 & 24 > http://bestpractical.com/training > > We're hiring! http://bestpractical.com/jobs > -- Best regards, Ruslan. -------- Final RT training for 2012 in Atlanta, GA - October 23 & 24 http://bestpractical.com/training We're hiring! http://bestpractical.com/jobs
