[rt-users] Comment/Correspondence Headers from WebUI

[Michael S. Liebman]

I'm noticing something slightly odd since upgrading to RT 3.2.0. When
displaying full headers in the Web UI, the headers for a comment or
reply will look like:

             MIME-Version: 1.0
             Content-Type: text/plain; charset="utf8"
                 X-Mailer: MIME-tools 5.411 (Entity 5.404)
      Content-Disposition: inline
Content-Transfer-Encoding: binary
   X-RT-Original-Encoding: utf-8
   X-RT-Original-Encoding: utf-8RT-Send-CC:
           Content-Length: 31

Note the second X-RT-Original-Encoding line and the absence of
RT-Send-BCC:.

Looking at the headers directly in the database, everything looks normal:

mysql> select Headers from Attachments where TransactionId=1955\G
*************************** 1. row ***************************
Headers: MIME-Version: 1.0
Content-Type: text/plain; charset="utf8"
X-Mailer: MIME-tools 5.411 (Entity 5.404)
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Original-Encoding: utf-8
RT-Send-CC:
RT-Send-BCC:
Content-Length: 31

This doesn't seem to be actually affecting anything other than
display. My best guess is something is going wrong in
/Ticket/Elements/ShowMessageHeaders or
/Ticket/Elements/ShowTransactionAttachments when it tried so localize
the headers, but that's as far as I'm getting in diagnosing.

Is this a real (non-critical) bug or am I missing something obvious?

Michael
-- 
Michael S. Liebman                      m-liebman at northwestern.edu
                  http://msl521.freeshell.org/
"I have vision and the rest of the world wears bifocals."
        -Paul Newman in "Butch Cassidy & the Sundance Kid"