We're upgrading to Exchange 07 from 03 and we're running into an issue with OWA. Blackberry Enterprise Server has an issue with S/MIME certificates in that a Blackberry device cannot process a message from OWA if the message is signed with the user's certificate. There are two behaviors: if the message just has the certificate attached, the Blackberry device gets an S/MIME error. If it is signed and encrypted, the message is never delivered. Blackberry has been working on the issue for two years, but we're not hopeful we'll see a solution from them soon. Our Exchange 2003 server allowed us to tweak the OWA code a bit by changing the doSend() function within frm_MimeNote.js to set g_objBody.signed = false. That meant that even if the message arrived with a digital certificate, it was stripped out before the message was replied/ forwarded, enabling the message to arrive on a Blackberry device. We're looking to do the same with OWA 2007. We need to strip out a digital certificate on reply/ forward if a message arrives with one. We also need to remove the signing button from the new e-mail toolbar. Any assistance with this is appreciated. - kb
Not a direct solution, but Blackberry has a unique solution for Cisco Unity voicemail that uses their MDS service. The plugin uses the blackberry API to notice any message with the Cisco voicemail attachment and it modifies the content sent to the device (without modifying the content of the message on the exchange store) such that you get a URL to trigger playing of the voicemail file. Could be a similar solution could allow you to either get at the plain text of the messages or just put in a URL so the blackberry would access the message over OWA using the blackberry browser. wild ideas wrote in message news:a963f0bc-34d9-4937-9180-a18c2a495736@f63g2000hsf.googlegroups.com... > We're upgrading to Exchange 07 from 03 and we're running into an issue > with OWA. Blackberry Enterprise Server has an issue with S/MIME > certificates in that a Blackberry device cannot process a message from > OWA if the message is signed with the user's certificate. There are > two behaviors: if the message just has the certificate attached, the > Blackberry device gets an S/MIME error. If it is signed and > encrypted, the message is never delivered. Blackberry has been > working on the issue for two years, but we're not hopeful we'll see a > solution from them soon. > > Our Exchange 2003 server allowed us to tweak the OWA code a bit by > changing the doSend() function within frm_MimeNote.js to set > g_objBody.signed = false. That meant that even if the message arrived > with a digital certificate, it was stripped out before the message was > replied/ forwarded, enabling the message to arrive on a Blackberry > device. > > We're looking to do the same with OWA 2007. We need to strip out a > digital certificate on reply/ forward if a message arrives with one. > We also need to remove the signing button from the new e-mail > toolbar. > > Any assistance with this is appreciated. > > - kb
