LO84879: SOME NOTICE REPLIES SENT BY TRAVELER SERVER INSTEAD OF USER.

IBM Traveler 9016 for Linux
IBM Traveler 9016 for Windows
IBM Traveler 9016 for IBMi

APAR status

• Closed as program error.

Error description

• Traveler users a newer Domino Java API to generate some reply
  notices when user takes action for event (not notice) from their
  device. These notices show up as sentBy the Traveler server and
  in some cases get duplicated in the cloud due to routing delays.
  Reverting to using Traveler code to build replies for cloud
  environment.
  
  For repeating events where the user uses accept/tentative from
  device calendar and there is no unprocessed meeting notice
  (invite,
  reschedule, infoupdate, etc) associated with that instance in
  the users mail db, then the resulting notice will still appear
  as
  being sent by the Traveler server on onbehalf of the user. This
  is case where user is changing an accepted instance to tentative
  or vice versa.
  This does not apply to declines, they should
  always by sent by user, not onbehalf of the user.
  
  The fix also addresses users getting the same notice sent over
  and over to chair due to device continuing to send notice for
  event already
  in the requested periodically.
  

Local fix

Problem summary

• Event notice may be sent multiple times or by the server user
  name vs the attendee or chair name.
  

Problem conclusion

• The IBM Traveler server was updated to resolve this issue.
  

Temporary fix

• This fix will be included in 9.0.1.6 and all future releases.
  See this technote for the latest maintence information for IBM
  Traveler.
  
  http://www.ibm.com/support/docview.wss?uid=swg24019529
  

Comments

APAR Information

• 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

  LOTUS NOTES TRA

• Fixed component ID

  5724E6204

Applicable component levels

• R901 PSY

     UP