RE: Exchange to MS POP
- From: v-terliu@xxxxxxxxxxxxxxxxxxxx (Terence Liu [MSFT])
- Date: Mon, 03 Mar 2008 10:17:50 GMT
Hello Customer,
Thank you for posting here.
According to your description, I understand that the email from your
Exchange 2003 to an POP server will be encoded thru base64 and unable to
read on the POP Server clients. If I have misunderstood the problem, please
don't hesitate to let me know.
Based on my research, I suggest we try the following steps to see if we can
resolve this issue:
1. Please install the following hotfix on your Exchange 2003. Or, ensure
you install Exchange 2003 sp2 on your server.
An Exchange Server 2003 recipient may receive a non-delivery report or an
e-mail message that is not formatted correctly
http://support.microsoft.com/?id=885419
An e-mail message may not be formatted correctly when a recipient sends the
e-mail message from an Exchange Server 2003 computer to another Exchange
recipient
http://support.microsoft.com/?id=835992
2. To specify e-mail format in Microsoft Office Outlook 2003 and earlier
versions of Outlook
Follow these steps to turn off TNEF:
a. On the Tools menu, click Options , and then click the Mail Format tab.
b. In the Send in this message format box, click Plain Text or HTML , and
then click OK .
Follow these steps to send in TNEF:
a. On the Tools menu, click Options , and then click the Mail Format tab.
b. In the Send in this message format box, click to select Microsoft
Outlook Rich Text Format , and then click OK .
3. May be the POP server unable to read the Microsoft plain text message.
Try to make the Exchange 2003 to send email thru HTML :
a. Open ESM, extend to Global Settings -> Internet Message Formats
b. Right click the Default line in the right panel, select properties
c. Select Message Format tab, select Provide message body as HTML, click OK.
d. Restart Exchange 2003 server.
Then, test this issue.
Additional information:
Frequently asked questions about MIME and content conversion in Exchange
2000 Server and in Exchange Server 2003
http://support.microsoft.com/?id=836555
If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:
1. Please try to send email to another POP server from your Exchange 2003,
does the issue reoccur?
2. Please try to forward the problematic email from the POP server to your
gmail mailbox. Does the message can be read?
I hope these steps will give you some help.
Thanks and have a nice day!
Best regards,
Terence Liu(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Exchange to MS POP
| thread-index: Ach7Ex+mbmeFMGlRQ3erfSYOVC1VSA==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?TWlrZSBLb2No?= <gsmike@xxxxxxxxxxxxxx>
| Subject: Exchange to MS POP
| Date: Fri, 29 Feb 2008 12:39:04 -0800
| Lines: 14
| Message-ID: <F0D41AFB-89F6-4B99-8BEF-9C83908EC98E@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2992
| Newsgroups: microsoft.public.exchange.admin
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.exchange.admin:62758
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.exchange.admin
|
| Our field users have handheld devices running Good Messaging, which is
| connected to our Exchange 2003 server. When they send mail to Outlook
clients
| (connected to the same Exchange server), the messages look fine. When
they
| send mail out to the internet, my gmail account, for example, they look
fine.
| When they send mail to our internal POP server (a standalone box in our
data
| center), the message body is a string of characters, whcih we eventually
| discovered is the base64 representation of the original message body. Any
| ideas why this is happening, and how I can stop it? The POP client is a
very
| simple app that doesn't know how to decode these messages, so the
messages
| are useless. And it's only the Good handhelds that exhibit this problem.
All
| other messages sent to the POP server deliver just fine as plain text
(the
| connector in Exchange is specifically configured to send only plain
text).
| We've been harassing Good about this problem, which just began with their
5.0
| release last fall, but so far no solution has presented itself.
|
.
- Prev by Date: Re: List of user which using autoforward
- Next by Date: Download Address Book Error
- Previous by thread: Re: List of user which using autoforward
- Next by thread: Download Address Book Error
- Index(es):
Relevant Pages
|
