3.0.2 incoming mail encoding problem (utf-8)

Hi.

I have a RT 3.0.2 running on postgresql 7.3 (UNICODE). Sending e-mail in
iso-8859-2 to rt-mailgate gives an entry in syslog:

RT: Converting ‘iso-8859-2’ to 'utf-8

and then non-ascii chars in database appear a little messed up, which is
quite normal to me, since Encode doesn’t support iso-8859-2.

But when I send an e-mail in utf-8 - nothing about conversions appears
in syslog, but characters in database are messed up too, just the same
way as with e-mail in latin2. Can anybody tell me where is the problem
or how can I try to debug this?

My charset setting from RT_SiteConfig is:

@EmailInputEncodings = qw(utf-8 iso-8859-1 us-ascii) unless (@EmailEncodings);

TIA

Richard.

“First they ignore you. Then they laugh at you. Then they
fight you. Then you win.” - Mohandas Gandhi.

Hi.

I have a RT 3.0.2 running on postgresql 7.3 (UNICODE). Sending e-mail in
iso-8859-2 to rt-mailgate gives an entry in syslog:

But when I send an e-mail in utf-8 - nothing about conversions appears
in syslog, but characters in database are messed up too, just the same
way as with e-mail in latin2. Can anybody tell me where is the problem
or how can I try to debug this?

Can you tell us if this still happens with RT 3.0.3pre3?

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

Hi.

I have a RT 3.0.2 running on postgresql 7.3 (UNICODE). Sending e-mail in
iso-8859-2 to rt-mailgate gives an entry in syslog:

But when I send an e-mail in utf-8 - nothing about conversions appears
in syslog, but characters in database are messed up too, just the same
way as with e-mail in latin2. Can anybody tell me where is the problem
or how can I try to debug this?

Can you tell us if this still happens with RT 3.0.3pre3?

Well, there is one more thing. It seems that the behaviour of
rt-mailgate depends on which queue I’m using. Is there something I’m
missing? One of them receives utf-8 characters correctly, the other -
not. Headers in table attachments are for both tickets identical, but
content - not.

Richard.

“First they ignore you. Then they laugh at you. Then they
fight you. Then you win.” - Mohandas Gandhi.

Can you tell us if this still happens with RT 3.0.3pre3?

Well, there is one more thing. It seems that the behaviour of
rt-mailgate depends on which queue I’m using. Is there something I’m
missing? One of them receives utf-8 characters correctly, the other -
not. Headers in table attachments are for both tickets identical, but
content - not.

With 3.0.2 or with 3.0.3pre3?

Richard.


“First they ignore you. Then they laugh at you. Then they
fight you. Then you win.” - Mohandas Gandhi.

Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.

Can you tell us if this still happens with RT 3.0.3pre3?

Well, there is one more thing. It seems that the behaviour of
rt-mailgate depends on which queue I’m using. Is there something I’m
missing? One of them receives utf-8 characters correctly, the other -
not. Headers in table attachments are for both tickets identical, but
content - not.

With 3.0.2 or with 3.0.3pre3?

With 3.0.2. After upgrading to 3.0.3pre3 problem disappears.

Regards,

Richard.

“First they ignore you. Then they laugh at you. Then they
fight you. Then you win.” - Mohandas Gandhi.