LO66618: DBCS FILENAME OF ATTACHMENT IS ENCODED BY WRONG CHARACTER SET.

APAR status

• Closed as unreproducible.

Error description

• If you send a mail with a attachment (filename is DBCS) from
  Notes Client , the filename of attachment is always encoded by
  UTF-8.
  In Japanese locale, although contents of subject and body is
  encoded by ISO-2022-JP (Japanese JIS Code) , filename is encoded
  by different character set (UTF-8/ISO-8059-1).
  Because of this , the subject/body or file name is garbled in
  many of mail applications.
  
  This problem is a regression problem from Notes 8.5.2 FP4.
  
  Steps to reproduce.
  1. Run Notes Client.
  2. Set "MIME Format" in [Format for messages addressed to
  internet addresses:] of location document.
  3. Attach a file with DBCS file name.
  4. Enter some DBCS characters in subject and body.
  5. Send the mail.
  6. Display MIME data in the mail.
  
  ** example **
  To: tesuto@teste.com
  MIME-Version: 1.0
  Subject: =?ISO-2022-JP?B?GyRCJCIkIiQiGyhC?=
  X-KeepSent: FFD312DE:9CA0D6E7-49257988:00379551;
   type=4; name=$KeepSent
  X-Mailer: Lotus Notes Release 8.5.2FP4 November 18, 2011
  Message-ID:
  <OFFFD312DE.9CA0D6E7-ON49257988.00379551-49257988.0030EEAA@Local
  Domain>
  From: Admin_Notes/852%852@test.local
  Date: Tue, 17 Jan 2012 19:07:31 +0900
  X-MIMETrack: Serialize by Notes Client on Admin
  Notes/852(Release 8.5.2|August 10, 2010) at
   2012/01/17 13:50:57
  Content-Type: multipart/mixed; boundary="=_mixed
  0030EEA849257988_="
  
  --=_mixed 0030EEA849257988_=
  Content-Type: text/plain; charset="ISO-2022-JP"
  
  ?$B$"$"$"?(B
  --=_mixed 0030EEA849257988_=
  Content-Type: application/rtf;
  name="=?UTF-8?B?44OJ44Kt44Ol44Oh44Oz44OILnJ0Zg==?="
  Content-Disposition: attachment;
  filename="=?UTF-8?B?44OJ44Kt44Ol44Oh44Oz44OILnJ0Zg==?="
  Content-Transfer-Encoding: base64
  
  e1xydGYxXGFuc2lcYW5zaWNwZzkzMlxkZWZmMFxkZWZsYW5nMTAzM1xkZWZsYW5n
  ZmUxMDQxe1xm
  b250dGJse1xmMFxmcm9tYW5cZnBycTFcZmNoYXJzZXQxMjggXCc4MlwnNmNcJzgy
  XCc3MiBcJzgy
  XCc2ZlwnODNcJzUzXCc4M1wnNTZcJzgzXCc2MlwnODNcJzRlO319DQp7XCpcZ2Vu
  ZXJhdG9yIE1z
  ZnRlZGl0IDUuNDEuMTUuMTUwNzt9XHZpZXdraW5kNFx1YzFccGFyZFxsYW5nMTA0
  MVxmMFxmczIw
  XCc4MlwnYTBcJzgyXCdhMFwnODJcJ2EwXCc4MlwnYTBccGFyDQp9DQoA
  
  --=_mixed 0030EEA849257988_=--
  
  Authogh filename was encoded by UTF-8, subject and body were
  encoded by ISO-2022-JP.
  In this case, the encoding of attachment should be ISO-2022-JP.
  

Local fix

• Use Notes 8.5.2 FP3 or Notes 8.5.3.
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# STAA8QLCMN.
  The change team could not reproduce the problem or determined
   that the problem has already been corrected.
  

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