IBM Support

LO54597: NOT LISTED IN DOMINO DIRECTORY ERROR OCCURS IN ROUTER IF JAPANESE NAME INCLUDES CODE 'F5' AND "_" CHARACTER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This problem occurs in Japanese character.  In this report,
    Capital letter describes a Japanese character.  Ex. KAMIYAMA.
    
    For example, if "KAMIYAMA_TARO/ORG@NotesDomain" is in SentTo
    field on a mail document, after the mail sending, "Delivery
    Failure Report" mail is received from Router.  The mail has the
    following description.
    because: User KAMIYAMA_TARO/ORG (KAMIYAMA_TARO/ORG@NotesDomain)
    not listed in Domino Directory
    
    If the user name has @NotesDomain, Notes client hands it to
    Router without looking for the user name in Domino directory.
    If Router can not look for it, Router sends back the error mail.
    This problem
    
    The following is Mail Router log in fact.
    2010/08/13 18:06:02   Router: Unable to deliver message 0031F32E
    to KAMIYAMA_TARO/ORG@rum from Ichiro Suzuki/org
    OF328C042E:1030B9D1 ON4925777E:0031F32E
    2010/08/13 18:06:02   User KAMIYAMA_TARO/ORG@org not listed in
    Domino Directory
    2010/08/13 18:06:02   Router: Delivery to local recipient Ichiro
    Suzuki/org is ready with 1 messages
    2010/08/13 18:06:02   Router: Delivery thread [0000000C]
    searching for work
    2010/08/13 18:06:02   Router: Message 0031FDC0, 0031F32E
    delivered to Ichiro Suzuki/org from Ichiro Suzuki/org
    OF1C1E38AF:65645222 ON4925777E:0031FDC0 Size: 1K Time: 00:00:00
    Hop Count: 2
    
    If user name includes underline character and the following
    Japanese characters, the error occurs.
    ex. KAMI, KUMO, TEN, etc
    
    The Japanese character is DBCS and consists of 2 bytes.  These
    characters has code 'F5' in the 2nd byte.   Underline is also
    code 'F5'.    Every 'F5' inside SBCS and DBCS replaced to space
    character.  It is thought that the Japanese character is damaged
    at the time of this replacement and that the error appears
    because Router can not search with the damaged Japanese name in
    Domino directory.
    
    Steps to reproduce
    1. Register a new user who has the name of Taro Kamiyama and his
    alternate name is  "KAMIYAMA TARO".
    (In this case, Organization name is "ORG")
    2. Choose "Alternate names" for Default display name in the
    Location document in Notes client.
    3. Open new mail form and write "KAMIYAMA TARO/ORG@NotesDomain"
    in SentTo field.   Notice: There is underline "_" between First
    name and Last Name.   The organization name and @domain name are
    added to it .
    4. Push Send button.
    You receive Delivery Failure Report from Router.
    
    Memo: If "YAMADA TARO" is registered, his name with underline
    can be sended.  "YAMADA_TARO" can be sended but "KAMIYAMA_TARO"
    can not.
    

Local fix

Problem summary

  • A programming error was found and will be corrected in a future
     release.
    

Problem conclusion

  • A programming error was found and will be corrected in a future
     release.
    

Temporary fix

Comments

  • This APAR is associated with SPR# YSAI894BVL.
    

APAR Information

  • APAR number

    LO54597

  • Reported component name

    NOTES CLIENT

  • Reported component ID

    5724E6255

  • Reported release

    851

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-09-08

  • Closed date

    2011-05-31

  • Last modified date

    2011-05-31

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

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

Fix information

  • Fixed component name

    NOTES CLIENT

  • Fixed component ID

    5724E6255

Applicable component levels

  • R851 PSN

       UP

[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTWP","label":"Lotus Notes"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
31 May 2011