Known Interoperability Issues and Limitations

Known interoperability issues

The HCL Notes client always saves encrypted Sent and Draft items with Notes Encryption, regardless of whether the corresponding message is eventually sent used S/MIME Encryption. As a result, if you use Notes to send an encrypted message to yourself using your Internet address, you have an S/MIME encrypted copy in your Inbox and a Notes encrypted copy in your Sent folder.

Sending an S/MIME signed message using HCL Verse iOS to an HTMO user results in the S/MIME signature of the received email in HTMO to be treated as untrusted. The S/MIME credential used to sign the message is valid, but a Traveler server issue is causing the S/MIME message to be altered resulting in the S/MIME signature to being untrusted when synced to an HTMO client. This issue is fixed in HCL Traveler Server 12.0.2 Fix Pack 1 (and higher). This does not affect S/MIME encrypted mail. For more information, see KB0102678.

Limitations

HCL Verse for iOS has a maximum data object sync size of 25MB which constrains the maximum email that can be sent from the device. In standard email transmission the overheard associated with encoding the email for transmission further reduces the maximum email size to approximately 17MB. S/MIME signed messages are also subject to the standard 17MB maximum.

Due to the increased overhead associated with S/MIME encryption, the maximum S/MIME encrypted email that can be sent from the device is approximately 12.8MB.

Smart-forward/Smart-reply capabilities are not applicable when interacting with S/MIME signed and/or encrypted messages due to the security requirements associated with S/MIME emails and the inability to make any changes to their content once they are signed or encrypted. This limitation requires that all attachments associated with S/MIME emails must be downloaded to the device before they can be sent in an S/MIME message.

Summary Sync will cause S/MIME messages that are older than the specified number of days old to be truncated. This causes HCL Verse iOS to incorrectly parse the email as S/MIME. Hence, for S/MIME encrypted messages the Status line displays the generic “this message is encrypted” line and a Download message button. Tapping on Download to retrieve the full message should display the correct status line for the S/MIME encrypted message. For truncated S/MIME signed messages, a Download message action will be displayed to retrieve the full S/MIME signed message the same way a standard message will be if it is truncated.

Changing the default encryption type of an S/MIME signed draft to Notes then sending the draft message as unsigned causes the S/MIME signature to be attached as an smime.p7s file on the received email. This is currently considered a limitation on Verse iOS.