asked on

Email sent from blackberry received with body blank

Hi. We recently purchased and set up a few blackberry 8300s to send/receive email via OWA. Some mail sent from the blackberry is received with a blank body. Blackberry support says that something on my Exchange server is reformatting the messages? Regular OWA via a computer has worked fine for the last 2 or 3 years since inception though so I'm at a loss as to what the difference would be with these devices. I'm a noob with the Blackberries so any insight would be great.
OWA is set up on a front end MS Server 2003 std, running Exchange 2003 std(SP 2).

Gary Cutri

This normally happens when the email being replied to was originally sent in Rich Text Format.

valmatic

ASKER

I thought it was some issue at the client level but why is Blackberry telling me it's an issue on the Exchange server? Are hey on to something or just blowng smoke to end the support call...
thanks :)

Gary Cutri

It is very common in a Domino environment for this to occur as you can see by this KB article:
http://www.blackberryforums.com.au/forums/ibm-lotus-domino/936-messages-replied-result-blank-body-receiving-end.html

Now to confirm, is it new emails being sent from the Blackberry that have a blank body or is it only replies to emails?

Gary Cutri

Also this issue can be caused if an email is MultiPart/Mixed meaning it could contain plain text and html.

ASKER CERTIFIED SOLUTION

Gary Cutri

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

valmatic

ASKER

gary, hi. thanks for all of the info.. This is happening on both new messages and replies - only sent from the blackberry device. This doesn't really apply to my environment but I think it points in the right direction. I did make a change on the exchange server to allow Rich Text and I set up OMA to test as well. Give me a day to get my hands on a blackberry and try it out...

valmatic

ASKER

Thanks again Gary. didn't really answer my question but I'll hand over the points anyway. Turned out to be an issue with an old spam filter that was left in place. Most of the rules are shut down on this filter but it doesn't handle mime too well. The vendor had a patch for this specific issue and that seems to have solved the problem.