LO88091: JAPANESE CHARACTERS DISPLAYED INCORRECTLY.

APAR status

• Closed as fixed if next.

Error description

• Japanese characters in the email that get sent (internally) were
  garbled while those received by other mail application(such as
  gmail) is viewed correctly.
  
  1. checked the following settings in
  natest-maildb25.notes.mckinsey.com
  and dev-tibcoint01.ads.mckinsey.com:
  
  a. MIME > Basics > Secondary Character set group > Please make
  sure
  that you have Japanese set here.
  
  b. MIME > Advanced > Advanced Inbound Message Options > Kindly
  check if
  you have character set name aliases set here. Make sure there
  is none.
  
  c. MIME > Advanced > Advanced Outbound Message Options > Kindly
  check
  if you have character set name aliases set here. Make sure
  there is
  none.
  
  2. Ran the following:
  
  tell touter update config
  restart task router
  restart task smtp
  
  3. Applied saveoutboundtofile from the sending
  server and smtpsaveimporterrors on the receiving end
  
  4.Comapared the MIME character set encoding
  being sent out by the TIBCO Server and the one being received
  by domino
  mail server and see if there are any conversion happening
  
  5. MR SWE take out 1 particular ST files uploaded based from
  the logs
  
  [1030:0009-0CA8] 12/09/2015 05:30:14 AM  SMTP Server:
  dev-tibcoint01.ads.mckinsey.com (157.191.239.139) connected
  [1030:0009-0CA8] 12/09/2015 05:30:14 AM  SMTP Server
  [1030:0009-0CA8]
  RFC822 message inbound stream saved to
  C:\Windows\TEMP\notes4F63E8\st169924.TMP
  
  And then did test this ST files on internal test server and the
  results are as follows:
  
  1. The rendering is incorrect when using Notes Client
  
  2. The rendering is good when using Outlook 2013 on the same
  email
  
  The router is not involved in any MIME
  conversion from the server level and the issue is probably
  coming in
  from the Notes Client side.
  
  6. Ask the original sender of the email to send the
  same garbled email to client SWE. As per original sender,the
  same
  emails are delivered with proper header
  (ie. charset: UTF-8) when sent to internet email services (such
  as
  gmail) or even other domino servers. - The issue did not
  persist when
  the email was received by the client SWE.
  
  7.  The email body (as HTML) stored in the Database is fetched
  and is
  sent directly using mailhub servers. The content type header is
  set to
  text/html with UTF-8 charset but when received by all Mckinsey
  users,
  the value for charset was changed to Cp1252.
  
  8. trapped the email before sending it out and ask customer to
  upload
  the mail.box
  -Confirmed the exact steps how the email was created
  ++ the email body (as HTML)
  stored in the Database is fetched and is sent directly using
  mailhub.mckinsey.com servers. The content type header is set to
  text/html with UTF-8 charset.As per mckinsey developer there is
  nothing
  else which could be provided to IBM regarding this.
  
  -Confirmed how the email was sent and if it uses a third party
  app
  ++they use TIBCO mailsend process to send the mail. The other
  routing
  or details are specific to the firm.
  
  9. Upon checking the emails trapped in the mail.box I found in
  the page
  source that before you send out the email, the charset is
  already set to
  Cp1252. This means that the value was already changed before
  you were
  able to send it.
  
  10. The emails with issue are triggered by the user
  using TIBCO application and it sends the email to intended
  recipients
  directly.
  

Local fix

Problem summary

• This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# MMNDA7F29S.
  This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

APAR Information

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

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

Fix information

Applicable component levels

• R901 PSN

     UP