|This topic describes known Windows™ Mobile device restrictions and limitations with IBM® Lotus Notes® Traveler.
This topic describes known Windows
Mobile® device restrictions and limitations with IBM
® Lotus Notes
For limitations and restrictions that apply to all device clients, refer to Server limitations and restrictions
Table 1. Install issues
Lotus Notes Traveler may conflict with other third-party sync solutions installed on a device.
Running Lotus Notes Traveler on the same device with other third-party syncing solutions is not supported. Doing so could result in data being lost, changed entries being missed, and decreased performance.
Some devices are not identified correctly for the purposes of suggesting the correct client download for the device.
The Moto Q WM6 Smartphone using the Opera browser is identified as Windows Mobile 5 instead of Windows Mobile 6.
The Samsung SGH-i600V WM 5 Smartphone is identified as Windows Mobile 6 instead of Windows Mobile 5.
Note: There is text directing the user to manually select the correct version to install if the identification is incorrect.
Cannot install an older client over a newer version
If for some reason you must install an older version of Lotus Notes Traveler on a device that already has a more recent version, you must uninstall the more recent version first. Then installation of the older version can proceed.
Table 2. Mail issues
Mail messages received with a Please reply by date do not display on to-do list.
When a mail message is sent with the Please reply by option, it normally displays in both the Inbox of the recipient and to-do list on the Lotus Notes® client. On the Lotus Notes Traveler client, it displays only in the Inbox.
Canceling a draft mail message also deletes previous draft versions of the message.
Selecting Menu > Cancel to discard a draft mail message also remove previously saved drafts of the message from both the client and the server.
Mail messages moved to a subfolder of the Inbox, Drafts, or Outbox folder are not displayed.
The Windows Mobile client allows for the creation of subfolders in the Inbox, Drafts, and Outbox folders, but the Domino® mail system does not. If the user creates such a subfolder on the device, the subfolder is not sent to the Domino server. The user is notified of this event.
If the user moves mail messages into the Drafts or Outbox folders from the Inbox or other folders, such changes are undone and the user is notified. The exception to this is that a message in the Drafts folder is allowed to move to the Outbox on the device, which then sends the message.
Soft reset may cause mail syncing and refresh.
Performing a soft reset of the client device may cause mail to sync with the server and refresh.
|Mail does not work with personal groups ||Because we do not support the synchronization of groups, emails sent to a personal group (one not defined in the Domino server's address book) are not delivered and are not able to be sent. |
Retrieve Full Email action is unavailable for draft messages.
Messages in a draft state cannot be retrieved using the Retrieve Full Email action.
Mail is not sent to reply-to addresses.
If a user replies to a mail message where the reply-to field is set to an address that is not the From address, the reply goes to the From address rather than the reply-to address.
Table 3. Calendar issues
A Windows Mobile calendar application may not send a decline notice.
Some versions of the Windows Mobile calendar application do not support sending decline notices to a meeting organizer when participants delete the meeting from their device calendars. A decline notice is not sent by the calendar application unless it displays a message specifically asking if the participant wants to notify the organizer of the decline response.
Some instances of a repeating meeting do not display.
If you create an infinite event from the device, the Lotus Notes Traveler server truncates the event to either 10 instances if yearly, or 250 instances for all others.
Calendar entries past the year 2067, on both the device and server, are not synced.
Unable to specify all options for Chair invitation, including adding/removing attendees on Smartphone.
This is a Windows Smartphone device software limitation. Windows Mobile Professional supports all functionality.
Unexpected behavior occurs when you delete a meeting on a Windows Mobile 6 device.
If you are listed as an attendee for a meeting that is on your device calendar, and you select to delete the meeting, you are asked if you would like to send a response to the organizer. If you select Yes, you are presented with a mail message form where you can enter response text. The To field in the form is left blank. Regardless of what you put into the To field, the response is sent to the meeting organizer, even if you leave the field blank.
Windows Mobile devices lock up when syncing large numbers of calendar entries while logging is enabled.
Some devices will lock up when syncing large numbers (500+) of calendar entries if logging is enabled. The work around is to disable logging or increase the log file size to 10000+.
Sending a meeting invitation fails if user names contain spaces.
If you use Reply or Reply All from a meeting entry and one or more recipients of the resulting email contain spaces in their address, sending fails for those recipients. This is due to a problem in the Windows Mobile Calendar application that does not handle spaces well. For example, the address Firstname Lastname/Company/GEO is incorrectly changed to Firstname<Lastname/Company/GEO> and sending fails. The workaround is to manually edit the address before sending.
|Invites are not sent to personal groups ||Because we do not support the synchronization of groups, calendar invites sent to a personal group (one not defined in the Domino server's address book) are not delivered and are not able to be sent.|
All-day invitations are converted to 16-hour invitations
Windows Mobile devices allow users to create all-day invitations. However invitations of this type are not supported by Lotus Notes. As a result, if a user creates an all-day invitation on the device, it is converted to a 4 AM - 8 PM meeting before being sent to invitees.
Table 4. To do issues
Unable to assign Group To-do
Group tasks cannot be assigned; this is a limitation of the Windows device software.
Table 5. Contacts issues
Contacts stored on a SIM card do not sync
Contacts stored on a SIM card are not synced by Lotus Notes Traveler; only contacts located in the Microsoft™ Pocket Outlook contact database are synced with the server.
Lotus Notes Traveler does not read or modify data on a SIM card directly. In order to sync contacts on a SIM card, certain phones include an application that allows the user to copy between their SIM card and the Pocket Outlook contact database. If the SIM contacts are copied to the Pocket Outlook contact database, they sync with the server mail file using Lotus Notes Traveler.
Names in Call History lost during initial or replace data Contact sync
Call history information is stored in a hidden field in the Contact Store. This hidden information is lost during an initial or replace data Contact sync. Subsequent syncs do not affect the call history. In all syncs, the phone number is retained in the call history, it is only the corresponding names that are lost.
Table 6. Notebook issues
Unable to create Notebook entry using a Windows Mobile 6 standard smartphone
This is a Windows Mobile device software limitation.
“Voice Notes” cannot be synced
Voice Notes is a separate application, and cannot be synced to the Lotus Notes Traveler client device.
Notebook entries are not synced.
Notebook entries are only synced from the server to the device. Any changes made to the notebook entries on the device do not sync back to the server.
Table 7. Policy issues
The Encrypt Storage card check box on Windows Mobile devices is not disabled when using Enforce violation action for Storage Card Encryption.
The device user can turn off Storage Card Encryption. However, the Lotus Notes Traveler client periodically (10 minutes) detects that the user has turned off Storage Card Encryption and turns it back on, as long as the Enforce violation action is in place.
Parent topic: Known limitations and restrictions