Skip to content

Assigning preferences and security settings to devices

There are different ways to assign settings that determine how users work with the HCL Traveler server. You can use the built-in set of default device preferences and security settings that HCL Traveler provides, which is simpler. Or you can create a HCL Traveler policy settings document, which provides greater flexibility and control but is more complex to configure.

If you are using a HCL Traveler policy settings document, the template of the address book on the HCL Traveler server should be at the latest Domino 901 pubnames.ntf template to ensure all the available tabs and settings are available.

Note: HCL Domino Workspace Mail for Android and iOS clients support being configured by third party Enterprise Mobility Managers (EMM). EMM supplied settings take precedence over Traveler settings (unless supplied settings are locked). It is recommended that all settings be managed via the EMM and not through the Traveler server or Traveler policies. For more information, see Managing Android Mail using Android Enterprise and Managing Mail for IOS using AppConfig.

  • Default device preferences and security settings
    HCL Traveler provides a built-in set of default device preferences and security settings that an administrator can modify for use when a device initially registers with HCL Traveler. Users can then modify their device preferences from their HCL Traveler device clients.
  • Creating an HCL Traveler policy settings document
    Use the HCL Traveler policy settings document to define device preferences and security settings for syncing Domino® user mail database data with their mobile devices.
  • Android Enterprise and Android Mail
    This topic highlights the Android Enterprise integration features that are included with the Android Mail application, and how to take advantage of it in your deployment.
  • Managing Mail for iOS using AppConfig
    This topic highlights the steps required for an Enterprise Mobility Management (EMM) administrator to deploy the Mail for iOS mobile app.
  • Device security
    There are a number of considerations to be aware of when securing different device types.
  • Working with attachment security settings
    You can control how HCL Traveler clients manage file attachments and images.
  • Remote wipe
    If a mobile device is lost or stolen, an administrator can issue a remote wipe command to remove all sensitive data from the device. You can remove the HCL Traveler application and data from the device and, depending on the device, restore the device to the factory default settings.
  • Console commands
    This topic provides a detailed description of the HCL Traveler console commands.
  • travelerUtil commands
    The travelerutil is a command line tool located in the <domino data>\traveler\util directory. Enter travelerUtil help while running the tool to display the full list of options.
  • Delegation support
    HCL Traveler can allow delegates to access mail files owned by other users.
  • Controlling access to HCL Traveler
    When a user leaves the company or a device is lost or stolen, you must remove or restrict access to the HCL Traveler server. This section covers methods for removing and restricting access.
  • Deleting a user from HCL Traveler
    An administrator can remove old or invalid users from the HCL Traveler database. This should only be done for users where access is already restricted using a HCL Traveler or Domino® server access list, or who are no longer listed in the Domino® directory.
  • Creating links to start the HCL Domino Workspace Mail mobile app
    Create links that a user can click to start the HCL Domino Workspace Mail mobile app from a web page or email.
  • Enabling syncing of read or unread changes
    Unread replication is enabled for each user automatically by the HCL Traveler server so that unread marks sync correctly with the device. This section explains how to activate unread replication manually using the Domino® Administrator client.
  • Repeated crash protection
    When certain Notes® documents are corrupted or contain non-standard content, they can cause the HCL Traveler server to repeatedly crash as it tries to process these documents. A repeating crash prevention feature exists to help minimize HCL Traveler server outage in these instances.
  • Maintaining the HCL Traveler database
    Whether running standalone HCL Traveler servers with the internal database or a pool of servers with an enterprise database, the database requires periodic maintenance to maintain optimal performance.

  • Mail address handling

  • Enforcing data sync limits
    Administrators can enforce synchronization data limits for all users using a setting in the Default Settings document.

  • Log types
    HCL Traveler has many different logs with a variety of purposes.
  • HTTP request handling and 409 responses
    HCL Traveler handles HTTP requests in specific ways that may result in 409 responses.
  • Confirming external recipients on Android devices
    For HCL Domino Workspace Mail for Android clients, you can choose to prompt the user to confirm the sending of mail to external recipients. This provides an extra step to help prevent the unintentional sending of mail outside of your organization.
  • Adaptive Initial Sync
    Adaptive Initial Sync (AIS) helps ensure server availability in certain server bring up or recovery situations. 
  • FCM messaging for HCL Domino Workspace Mail for Android clients
    HCL Traveler server can use Firebase Cloud Messaging (FCM) for real time push notifications to keep your Mail, Calendar, Contact and To Do data on your HCL Domino Workspace Mail for Android clients up to date. Google has deprecated GCM and replaced it with FCM.
  • APNS messaging for HCL Domino Workspace Mail for iOS clients
    HCL Traveler server can use Apple Push Notification service (APNs or APNS) for real time push notifications to keep your Mail, Calendar, Contact and To Do data on your HCL Domino Workspace Mail for iOS/iPadOS clients up to date.

  • How synced data moves through the system

  • How HCL Traveler processes attachments
    There are several issues to be aware of in how HCL Traveler processes attachments. 

  • How HCL Traveler processes SmartForward/SmartReply requests
    A SmartForward/SmartReply (SFSR) request is an email that is a forward or reply of a previously received email that does not include the body or attachments from the original email which is being forwarded or replied to. Instead, a SFSR contains just the forward/reply body text and any additional attachments, plus an identifier of the original email.

Parent topic:Administrative Tasks