On 11/21/2012 02:01 PM, David Moreau Simard wrote:
Hey there,
Just wanted to confirm that it does seem to be a regression.
https://github.com/bestpractical/rt/commits/3.8-trunk/lib/RT/I18N.pm
https://github.com/bestpractical/rt/commit/ccafbd233e4f50bd8ef1889949e91dc6190f495b
That eval
Hey there,
Just wanted to confirm that it does seem to be a regression.
https://github.com/bestpractical/rt/commits/3.8-trunk/lib/RT/I18N.pm
https://github.com/bestpractical/rt/commit/ccafbd233e4f50bd8ef1889949e91dc6190f495b
That eval seems to be necessary to have a Fallback encoding if an
What kind of information would you need to further confirm the issue on
the 3.8.x branch ?
I'd gladly pass along the information.
Thanks !
*David Moreau Simard*/
IT Specialist/
On 12-11-14 9:49 AM, Kevin Falcone wrote:
On Wed, Nov 14, 2012 at 08:51:06AM -0500, David Moreau Simard wrote:
On Wed, Nov 14, 2012 at 08:51:06AM -0500, David Moreau Simard wrote:
Chiming in to say that we're also having this issue on RT version 3.8.15.
This other thread also references the issue:
http://www.gossamer-threads.com/lists/rt/users/108219
Should we expect a fix on the 3.8.x branch as well
We recently had a request submitted to our RT system (version 4.0.4 on
a Linux Mint 13 box) that caused a crash. I have narrowed this down to
the fact the e-mail had a header that read Content-Type: TEXT/PLAIN;
charset=X-UNKNOWN; format=flowed and this caused RT to crash:
cse-rt ~ # cat
Hi,
We have a branch that improves sitatuation with unknow encodings. It
will be part of future 4.0.x releases.
On Mon, Nov 12, 2012 at 8:16 PM, sac s...@cse.unl.edu wrote:
We recently had a request submitted to our RT system (version 4.0.4 on a
Linux Mint 13 box) that caused a crash. I have
