IV95312: TRIRIGA INCOMING MAIL AGENT DOES NOT PROCESS EMAILS PROPERLY WHEN THEY ARE SENT BY APPLE MAIL CLIENT

3.5.2-TIV-TAP-FP002-WIN
3.5.2-TIV-TAP-FP002-README
3.5.2-TIV-TAP-FP002-LIN
3.5.2-TIV-TAP-FP002-AIX

APAR status

• Closed as fixed if next.

Error description

• When emails are sent to TRIRIGA using Apple's Mail client, they
  are not always being interpreted properly on the TRIRIGA end.
  Some problems seen have been these:
  
  -- When a Rich Text email is sent using Apple's Mail client and
     has an attachment, the attachment isn't seen if email history
     is present as part of the email.  If the email history is
     removed, the attachment is seen.
  
  -- When a Plain text email is sent using Apple's Mail client and
     a PNG or JPG attachment is present, the attachment isn't seen
     but the email body has a marker that makes it look like an
     embedded image should be present (but isn't).
  
  -- When a Plain text email is sent using Apple's Mail client and
     text exists in the email before the attachment, the text that
     exists in the email before the attachment isn't seen.  Any
     text that exists after the attachment is seen.
  

Local fix

• If you are using Apple's email client and all you are interested
  in TRIRIGA seeing is the attachment, do one of two things:
  
  - If you are using Rich Text when sending the email and need
    to stick with sending the email as Rich Text, remove the
    email history before sending.
  
  - If you are using Rich Text when sending the email but
    switching to using Plain text instead is an option, switch
    to Plain Text (Format => 'Make Plain Text') and send the
    email.
  
  If you are using Apple's Mail client and you interested in
  TRIRIGA seeing text in the email as well as the attachment, send
  the email as Plain Text (Format => 'Make Plain Text') and make
  sure that any text you want to have seen is found in the
  email _after_ the attachment.
  

Problem summary

• Apple mail formats attachments and forwards different that
  other mail clients.
  

Problem conclusion

• An issue that cause attachments to be missing and email message
  bodies to lose content when the mail client puts attachments
  inline has been resolved.
  This is targeted to the 1h2017 release as well as the 3.5.2.2
  fix pack.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• 999
  

Fix information

Applicable component levels