Last week or so, we’ve gotten many curious responses from yahoo mail
users who are reporting blank ticket responses. Sure enough, if you
correspond with our RT 3.2.3 instance via yahoo, all you see is the
headers. If you click the little link on the lower right corner of
yahoo’s mail to “save message text” you see the content. In the main
window you do not. I’m suspecting it has something to do with RT
setting the encoding to utf-8.
Last week or so, we’ve gotten many curious responses from yahoo mail
users who are reporting blank ticket responses. Sure enough, if you
correspond with our RT 3.2.3 instance via yahoo, all you see is the
headers. If you click the little link on the lower right corner of
yahoo’s mail to “save message text” you see the content. In the main
window you do not. I’m suspecting it has something to do with RT
setting the encoding to utf-8.
Has anyone else seen this?
Yes. Search for Content-Encoding 8bit and 8-bit. It’ll be fixed in
3.2.4/3.4.2
Any early patches/workaround available? Our customers are getting
annoyed
Er, yes. Documented in the thread. Nuke the hyphen.
I must be dense since I can’t find any threads related to utf8 messages
in the rt-users or rt-devel archives going back to february (not that
they are easily searched, either). I found one thread related to utf-8
subject lines, though.
Any early patches/workaround available? Our customers are getting
annoyed
Er, yes. Documented in the thread. Nuke the hyphen.
I must be dense since I can’t find any threads related to utf8 messages
in the rt-users or rt-devel archives going back to february (not that
they are easily searched, either). I found one thread related to utf-8
subject lines, though.
Sorry. My fault. I meant 8-bit/8bit, rather than utf-8/utf8.
Any early patches/workaround available? Our customers are getting
annoyed
Er, yes. Documented in the thread. Nuke the hyphen.
I must be dense since I can’t find any threads related to utf8
messages in the rt-users or rt-devel archives going back to february
(not that they are easily searched, either). I found one thread
related to utf-8 subject lines, though.
Sorry. My fault. I meant 8-bit/8bit, rather than utf-8/utf8.
RT Administrator and Developer training is coming to your town soon!
(Boston, San Francisco, Austin, Sydney) Contact training@bestpractical.com
for details.
RT Administrator and Developer training is coming to your town soon!
(Boston, San Francisco, Austin, Sydney) Contact training@bestpractical.com
for details.
I too have been receiving emails from @yahoo.com , @sbcglobal.net and @earthlink.net saying that they are receiving blank replies. (RT 3.4.1)
I’m still perplexed as to where I was expected to search for this fix,
as nothing was obvious in either the rt-users or rt-devel mailing lists
for the last three months.
