Tickets :: Comment on [#12970] Don't override sticky OPTIONS values with default values.

* Your Email Address
* Spam protection	Enter the letters below: . . __ .__ . .\ / \| \|/ `[__)\|_/ >< \|/\\|\__.\| \\| \/ \
Comment	> With the latest release of all the core modules, I did 4 tests: > #1 Send a S/MIME signed message from Thunderbird > #2 Send a S/MIME encrypted message from Thunderbird > #3 Send a S/MIME signed message from a BlackBerry 10 device > #4 Send a S/MIME encrypted message from a BlackBerry 10 device > > I then used Thunderbird, IMP and a BlackBerry 10 device to check the > messages. > > On Thunderbird > No problem with any of the messages. They are identified as signed or > encrypted and are successfully verified/decrypted. > > On IMP > - Signed message #1 shows this error message: "Message verified > successfully but the signer's certificate could not be verified". The > certificate is in the addressbook and the public key is stored in IMP > though. > - Encrypted message #2 is successfully decrypted. > - Signed message #3 shows this error message: "Verification failed - > an unknown error has occurred.". The public key is not in the keyring > and IMP doesn't offer to install it (but that could be because of a > problem with Turba's default addressbook) > - Encrypted message #4 shows: "Could not decrypt S/MIME data.". No > error in the logs. > > On BlackBerry 10 device via ActiveSync > - None of the messages are identified as SMIME as far as I can tell > - Encrypted message contains an attachment which is detected as a > "MIME Encrypted Message" and there is a green "tick" indicating it's > valid, but when tapping on it, the device indicates that there is no > viewer for it on the device. >
Attachment
Watch this ticket

Saved Queries