IBM Support

LO53105: EXHAUSTIVELY CHECK CAUSES LOTUSSCRIPT TO FAIL SENDING AND DO NOT NOTIFY THE USER.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as fixed if next.

Error description

  • You attempt to send a document from Lotus Notes® or Lotus
    Domino® using the LotusScript NotesDocument Send method.
    Having the features "Recent Contacts" and "Exhaustively check
    all address books" enabled can under certain circumstances
    result in no or partly mail sending without notifying the user
    doing the send.
    All tests done as front-end document processing.
    
    1. Recipient(s)
    One recipient with an ambiguous name
    
    Methods:
    - @mailsend / uidoc.send
    Results
    - "Ambiguous name" dialogbox opens.
    - User can select a name, and the mail will be sent
    
    Methods
    - evaluate(|@mailsend|, doc)
    Results:
    Nothing happens
    - No mail sent
    - No errors/warnings
    just an entry in the local log.nsf: "Unable to send mail to ..."
    
    Methods
    - doc.send(false )
    Results:
    "Unable to send mail" dialogbox opens.
    User can only select 'OK' - no mail sent
    
    
    2. Recipient(s)
    Two recipients, one with an ambiguous name (A) and one with an
    unique name (B)
    
    Methods:
    - @mailsend / uidoc.send
    Results
    -"Ambiguous name" dialogbox opens.
    User can select a name, and the mail will be sent to both
    recipients
    
    Methods
    - evaluate(|@mailsend|, doc)
    Results:
    -One mail is sent to (B)
    No mail is sent to A. No errors/warnings but an entry in the
    local log.nsf
    
    Methods
    - doc.send(false )
    Results:
    -One mail is sent to (B)
    No mail is sent to A.
    No warnings/errors, not even in the local log.nsf
    

Local fix

  • This issue is a particular case described in the Technote
    1153854.
    
    This issue was reported to Quality Engineering as SPR#
    EMMS2YMU3J and was found to be a software limitation.
    
    Workarounds:
    When a SendTo entry specifies a domain name, no initial
    validation of the entry is performed but the router still
    evaluates the SendTo field as usual.
    
    Workaround 1:
    Append the domain name to the end of the SendTo value, as in:
    
    Call doc.send(True, "Jane Doe/US/Widgets@Widgets")
    
    Additionally, if you want to have a duplicate entry in your
    Personal Address Book, copy the entry from the Domino Directory
    (People view --> highlight the person --> choose Edit --> Copy)
    and paste it into your Personal Address Book (People view -->
    choose Edit --> Paste). This will eliminate the error.
    
    Workaround 2:
    This is sample code to add the domain name automatically if an
    "ambiguous name" error occurs.
    
    NOTE: The code below is a sample script, provided to illustrate
    one way to approach this issue and is used at your own risk. In
    order for this example to perform as intended, the script must
    be laid out exactly as indicated below. Product Support cannot
    customize this script for specific environments or applications.
    
    Before the Send button, add the following:
    ...
    ...
    ...
    On Error 4294 goto AmbiguousError doc.send(True)
    ...
    ...
    ...
    Exit sub
    
    AmbiguousError:
    Set namesdb= session.getdatabase(db.server, "names.nsf")
    Set Persondoc=
    namesdb.getview("($Users)").getdocumentbykey(docmail.SendTo(0))
    docMail.SendTo = Persondoc.fullname(0)  & "@" &
    Persondoc.MailDomain(0)
    Call docMail.Send(True)
    Resume next
    End sub
    
    In this particulare case, customer has to programmatically
    add @org to all emails addresses
    

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# RGAU876G88.
    This APAR is closed as FIN. We have deferred the fix to a
     future release.
    

APAR Information

  • APAR number

    LO53105

  • Reported component name

    NOTES CLIENT

  • Reported component ID

    5724E6255

  • Reported release

    851

  • Status

    CLOSED FIN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2010-07-08

  • Closed date

    2016-02-29

  • Last modified date

    2016-02-29

  • 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

  • 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:
29 February 2016