LO86630: MAAS360 SECUREMAIL CLIENT ON IOS NOT GETTING MAILS WITH THE LINK TO COMPANION
Direct links to fixes
Closed as program error.
Traveler has the concept of a DeviceType which is used to determine what type of device it is based on device id, user agent, and other inputs. Whether operations were supported or not is then controlled per DeviceType. If this was working before, it means the DeviceType as the Apple mail client and not the MaaS360 SecureMail client as the M360 client was not in the list of devices that supported the Companion and therefore wouldn't get the download link - as the customer noticed. What has probably happened is that the DeviceType classification got fixed, and when it did, it really was the M360 client which wasn't allowed to have Companion links. Therefore, it was previously working as a side effect of another bug and once that bug was fixed, the side effect went away. However, it is easy enough to add M360 for iOS into the list of DeviceTypes that are allowed to use Companion on iOS. The APAR will add that function.
You could change the notes.ini DEVICE_TYPE values to force the MaaS360 Client on iOS to be classified as the Apple client, but that is untested and might have other side effects.
IBM Traveler server was not sending a Companion Application link for encrypted mail to Maas360 Secure Mail client on Apple devices.
The IBM Traveler server has been updated to send an IBM Companion compatible link for Domino encrypted mail when syncing with the Mass360 Secure Mail application on Apple devices.
This fix will be included in IBM Traveler 126.96.36.199 and all later releases. See this technote for the latest release information. http://www.ibm.com/support/docview.wss?uid=swg24019529
Reported component name
LOTUS NOTES TRA
Reported component ID
NoSpecatt / Xsystem
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