Final update: this issue is fixed. At the site in question, the
procmail-related “formail” application is being used to remail messages to
RT. During the remailing process, “formail” was stripping off the
"Content-Transfer-Encoding" and “Content-Type” headers from the incoming
message before remailing to RT.
Now that “formail” is configured to no longer strip those important headers,
RT is correctly able to discern that the message is Base64 encoded used and
RT-3.6.3 is correctly decoding the message.
From: Patrick Hess [mailto:email@example.com]
Sent: Friday, January 21, 2011 10:53 AM
Subject: Base64 encoded emails unreadable
The entire content of emails, not just attachments, from BlackBerry devices
appears to be Base64 encoded. The issue that we’re having is that RT-3.6.3
is unable to detect that the message is encoded – even though the
"Content-Transfer-Encoding header" is set to “base64” – and therefore any
message from a BlackBerry is unreadable.
I’m fairly certain that someone else has seen this problem and fixed it; I’m
hoping someone can give a recommendation to help with this. I am running
RT-3.6.3 on a RHEL4u5 x64 server with perl-5.8.5 using the