IBM Traveler 188.8.131.52 enabled by default a feature that allows Traveler to "Run as a User" instead of as a server. This feature resolves several long standing issues with accessing the user's data as the server ID, including:
- Preventing event notices and automated responses from being sent “from” the Traveler server ID (they are sent “from” the user ID instead)
- Preventing the server ID from being assigned as the owner of the mail profile when there is no owner defined.
- Honoring access controls on the mail file and corporate lookup for the user.
- The last point above may cause sync issues for mobile users. If the access controls are inadvertently set to values that restrict individual users, but do not restrict the Traveler server, then users that could sync when running as the Traveler server ID might not be able to sync when running as their user ID.
The IBM Support document describes the access controls, and the symptoms seen by the Traveler administrator when the controls are set to values which restrict users access.
Traveler 184.108.40.206 introduces enhancements to the messaging, to make it easier for the administrator to identify which access control is causing the sync issue. Traveler 220.127.116.11 also introduces a modification to the Run as User feature, that enables users to sync even if one of the access controls is configured in a restrictive way.
More information: How to resolve synchronization issues that start after upgrading to IBM Traveler 18.104.22.168 (or higher)