Forwarded tickets show as MIME-encoded attachments within attachments

When forwarding tickets (or a single ticket transaction) in RT 3.8.7, RT
generates an email with an attachment, and within that attachment is
another MIME encoded attachment. This is not very useful, at least not
in Outlook or Thunderbird. Is there a way to reduce the number of times
the ticket content gets wrapped up in attachments (and maybe send as
plaintext instead of MIME encoded)? I couldn’t find anything in
RT_Config.pm about ticket forwarding behavior. Thanks!

RT 3.8.7 running under Apache 2 with FastCGI, email is configured as:
Set($MailCommand , ‘sendmail’);
Set($SendmailArguments , “-oi”);

I also would like to know more about forwarded tickets. I get the same
behavior as the previous poster.

Nick Kartsioukas-3 wrote:

When forwarding tickets (or a single ticket transaction) in RT 3.8.7, RT
generates an email with an attachment, and within that attachment is
another MIME encoded attachment. This is not very useful, at least not
in Outlook or Thunderbird. Is there a way to reduce the number of times
the ticket content gets wrapped up in attachments (and maybe send as
plaintext instead of MIME encoded)? I couldn’t find anything in
RT_Config.pm about ticket forwarding behavior. Thanks!

RT 3.8.7 running under Apache 2 with FastCGI, email is configured as:
Set($MailCommand , ‘sendmail’);
Set($SendmailArguments , “-oi”);


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

View this message in context: http://old.nabble.com/Forwarded-tickets-show-as-MIME-encoded-attachments-within-attachments-tp27080149p27857482.html

Last I checked this is not an entirely accurate description.
RT sends the message as Content-type: message/rfc822
Messages are MIME, but only encoded if required.
Although few MUA seem to handle this well, it is the right
thing to do. The only iffy thing is that the outer layer used
to group multi-part messages is not necessary and un-
necessary obfuscation of single-part transactions.