Error: "This Device doesn't support encryption features" When Launching WorxMail on Android M Devices

The following error is displayed when launching WorxMail on Android M devices:
This Device doesn't support encryption features

The WorxMail logs show the following error:

 Line 233: 702 = EncryptionInitFailed Line 254: encryptionVersion = 2 Line 276: privateFileEncryption = SecurityGroup Line 277: publicFileEncryption = SecurityGroup Line 300: 702 = EncryptionInitFailed Line 322: 702 = EncryptionInitFailed Line 325: 2016-01-15T00:07:52.876+0200        MDX-PolicyAlert        INFO      ( 4)        This device does not support encryption features required by the application.        9899        9899        WorxMail                            0                                                                                         Line 349: 702 = EncryptionInitFailed Line 370: encryptionVersion = 2 Line 392: privateFileEncryption = SecurityGroup Line 393: publicFileEncryption = SecurityGroup Line 406: 702 = EncryptionInitFailed Line 420: 702 = EncryptionInitFailed Line 423: 2016-01-15T00:10:33.085+0200        MDX-PolicyAlert        INFO      ( 4)        This device does not support encryption features required by the application.        9899        9899        WorxMail                            0                                                                                         Line 464: 2016-01-15T00:10:35.255+0200        MDX-Application        WARNING   ( 3)        Failed to install Encryption Hooks        11216        11216        WorxMail                            0                                                                                         Line 480:   WrongEncryptionKeys = 108 Line 513:   EncryptionNeedsAuth = 504 Line 514:   EncryptionNeedsKeys = 505 Line 540:   EncryptionInitFailed = 702 Line 562:   EncryptionNotSupportedHoneycomb = 1003

Complete one of the following procedure to resolve this issue:

• Warp WorxMail application with the latest MDX toolkit 10.3.1. After the application is re-wrapped upgrade or push the application to Android M devices.

• To workaround this issue disable encryption in MDX policies.

  

This is a known issue when encryption is enabled.