Although I am using 0365, I think this is an Exchange issue and am posting here:
The short story:
Hello, it seems internal mailbox to mailbox Exchange is always text/html mime format. How can I force it to be multipart/alternative. My CRM application does not understand the text/htm.
The long story:
I have a CRM application that fetches mail with POP3, it works fine when clients send me email and I pop it from 0365 mailbox. Most all of the email headers that come in show Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CECE58.DA861F0C"
When I reply to a message, the outgoing format ends up being
" Content-Type: text/html; charset="us-"
My CRM cannot display it. I believe text/html is proprietary to Microsoft.
This might have something to do with the email being transported internally within Microsoft servers, because when I send my reply, I reply to the same mailbox, and my CRM email connector handles the routing.
Here I will try to explain:
1.) Message sent from client to support@ mailbox
2.) CRM pickups the mail with POP3
3.) Reply is composed in Outlook and sent from CRM to
support@mailbox (has a ticket number in the header to identify)
4.) CRM pickups the email with Pop3 and sends along to recipients which are defined in the CRM. The reply email is sent using O365 SMTP mail server.
All the mail routing is fine, everybody gets their mail, however the body of the message will not show up in the CRM because it does not understand the text/html.
How can I force my (Exchange server to server) messages to be multipart/alternative ?
* I have tried disabling TNEF for default.
* I have tried confguring messageretrievalmimeformat for types 0-6 below:
Set-PopSettings -Identity CAS01 -MessageRetrievalMimeFormat TextOnly
Text
0 or TextOnly
HTML
1 or HtmlOnly
HTML and alternative text
2 or HtmlAndTextAlternative
Enriched text
3 or TextEnriched
Enriched text and alternative text
4 or TextEnrichedAndTextAlternative
Best body format
5 or BestBodyFormat
TNEF
6 or Tnef
None of them make a difference. The messages still show up as text/html in the header. Other than routing my mail through a Gmail SMTP server and faking it out with my support@ address, I'm not sure what I can do but move back to a $3.00 per month pop server.