LO84879: SOME NOTICE REPLIES SENT BY TRAVELER SERVER INSTEAD OF USER.
Direct links to fixes
Closed as program error.
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.
Event notice may be sent multiple times or by the server user name vs the attendee or chair name.
The IBM Traveler server was updated to resolve this issue.
This fix will be included in 18.104.22.168 and all future releases. See this technote for the latest maintence information for IBM Traveler. http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
LOTUS NOTES TRA
Fixed component ID
Applicable component levels