IBM Support

LO70363: REPLY TO ALL THE MESSAGE FROM NON-ADJACENT DOMAIN, IT BECOME NDR

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • If the user send a message to multiple person at  a non-adjacent
    domain, user add entire domain information wihin the address.
    When one of the recipients at  the non-adjacent domain do "Reply
    to All", the address of other recipients at  same domain become
    invalid.
    
    Steps:
    1. Prepare four domino server as the following. Each server
    belong to different organization and domain. org and orgb, orgc
    is non-adjacent domain
    
    org domain <-->  orga domain <--> orgb domain <--> orgc domain
    
    2. from org domain user, send message to orgc domain user as the
    following.
    
    Send To:   Tom/orgc@orgc@orgb@orga, Bob/orgc@orgc@orgb@orga
    From:  Taro/org@org
    
    3. Tom/orgc@orgc receive the message. and Do "Reply to All"
    
    4. The address become the following.  Though Bob is in same
    domain, entire domain information is remains.
    Send To:  Taro/org@org@orga@orgb
    Copy To:  Bob/orgc@orgc@orgb@orga
    From: Tom/orgc@orgc
    
    5. Send the message
    <PROBLEM>
    If there is no non-adjacent domain document of orga in orgc's
    NAB,   Bob cannot receive the message. it become NDR.
    If there is a non-adjacent domain document of orga in orgc's
    NAB,   the message can deliver to Bob successfully.    However
    unnecessary transferring is occurred to external domain.
    
    If the address is local domain user,  it should be stipped off
    the unnecessary domain information.
    

Local fix

  • To avoid NDR,  create non-adjacent domain document.
    

Problem summary

  • Low priority closures
    

Problem conclusion

Temporary fix

Comments

  • This APAR is associated with SPR# CSAO8VW8VT.
    This was closed as part of a batch closure of sprs with minimal
     customer impact. Low weight, Sev 3 or lower, and a defect
     creation date of 12/31/2012 or earlier. If this issue persists
     in 9.0.1 or above by additional customers, it may be re-raised
     for triage.
    

APAR Information

  • APAR number

    LO70363

  • Reported component name

    DOMINO SERVER

  • Reported component ID

    5724E6200

  • Reported release

    852

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-07-05

  • Closed date

    2014-03-04

  • Last modified date

    2014-03-04

  • 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

  • R852 PSN

       UP

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

Document Information

Modified date:
04 March 2014