Hello, We have an exchange 2003 server that is having a problem sending email to mobile phones via a txt message. For example I send a email to 1112221234@vtext.com it sends the message but on the other end it show up like this /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri","sans-serif";} a:link, span.MsoHyperlink {mso-style-priority:99; color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {mso-style-priority:99; color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri","sans-serif"; color:windowtext;} .MsoChpDefault {mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} With the message correctly showing after this. Any help or suggestions would be appreciated.

I think is rather client issue than server issue. What are your clients on both ends? If you are using Outlook to send mail from, are you selecting message format to be plain text?With kind regards Krystian Zieja http://www.projectnenvision.com Follow me on twitter My Blog

Hi, What's your mobile device? Do you connect to exchange by pop3 or activesync?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Thanks Gen Lin-MSFT

Its looking encoding problem at mobile device. are you able to send correct format text message to any other model of device.Anil

Thanks to all who are responding, sorry it took me so long to respond back. We are generally using Microsoft Outlook 2003, 2007, or 2010 to send the message out. The mobile device is an android 2.2 MyTouch3G I’m thinking it’s on the client side but we are still having the issue...