[hzgjlv]

More info from RIM regarding a fix in reply to a question regarding rolling back to MR2

"I saw today that there was an escalation based on swapping the
binary files (for the MR2 binary files) as a workaround for this issue.
I would advise waiting until the results of that testing come back as we
might be able to do a simple swap of some files rather than the process
mentioned above. Having said that, I have no idea how long this testing
will take to complete and it was only requested today.

[dalewest]

@mahoward, thanks again for sharing. My users are now running keyless (which is fine, since 90% of them haven't attached their Notes IDs to their DWA).

[Jadey]

Originally Posted by dalewest

mahoward and hzgjlv, I'm seeing the exact same thing as you, and I'm on BES 4.1.6 MR3, Interim Security Update 2 (the ISU 2 is highly recommended, BTW, as it fixes a nasty PDF vulerability), running on Domino 7.0.3FP1.

Me too! MR3'd (and ISU2'd it) on Sunday, started noticing this today.

Should have paid more attention to this thread, my bad

[mahoward]

Just to reiterate, you can get rid of this issue by applying the following change which will disable native notes encryption support on the BES:

Complete the following steps:

1. Open the Registry Editor.
2. Go to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Research In Motion\BlackBerry Enterprise Server\Agents
3. Create a new DWORD Value with the name SECMSGSupported.
4. Set the value of the key to 0.

[Jadey]

mahoward, you are my hero, have an award!

[BBFlunkie]

We've tried and we're unable to consistently create the message.

[x14]

This is fixed in 4.1.6 MR4.

[BBFlunkie]

>>Create a new DWORD Value with the name SECMSGSupported

This worked. The "false-encrypted signed" messages are no longer a problem.

We are reviewing MR4, not yet commited to install it.

[Phoenix887]

X14 have you applied MR 4 ?

[pomc]

Just to provide an update for anyone still on MR3 - there is a "better" RIM approved fix than the registry edit. RIM T-Support didn't recommend the registry edit since it could make a message body appear empty.

We're at Domino 8.02, BES 4.16 MR3, so this would appear to work for Notes only, unless there is a corresponding policy for Exchange BES. We just began seeing this problem yesterday after upgrading from Domino 7.02 to 8.02 with no change to the BES.

Instead, edit the IT Policy - Email Messaging policy group - Disable Notes Native Encryption Forward & Reply - True

This has been tested and works...the signed messages arrive on the BlackBerry without incident or prompting.....but of course the user cannot reply or forward the message.