In Transaction_Overlay.pm, the ContentObj method assumes that the content is
in the transaction’s first attachment. This appears not always to be the
case - we have several tickets created through the email interface in which
an attached binary file is the first attachment, and the email message is
stored in subsequent attachments. This has caused the default global
template to fail (it does a $Transaction->ContentObj->Headers call, and
ContentObj is null in this case).
I’m wondering where the fix should be. Should the content always be in the
first attachment, as the ContentObj method assumes? If so, is this a problem
in the incoming email interface - i.e. is it storing the attachments from
incoming email incorrectly?
Senior Programmer/Analyst - Client Support Services
MIT Information Services and Technology (IS&T)