PDA

View Full Version : Office 365 not displaying emails correctly


Araphael
April 26th, 2012, 10:54 AM
We recently switched our email provider to Microsoft Office 365. Just like with our previous provider, we have to use stunnel to connect and download emails intoCommitCRM. While there is no problem with the emails displaying properly for the client or for us, in CommitCRM I only see this:
< The textual email content cannot be displayed. No text/plain section found. Use the ‘Show Original’ option to view the message in your email client application >

It seems like somewhere in Office 365 the plain text is stripped out of the HTML email. I don't know why this would happen. Has anybody experienced this before? Anybody else on Office 365 for their email?

Thanks!

racassel
September 18th, 2013, 11:27 AM
I am havin the same problem and am fixin to give them a call. Did you get this resolved?

Support Team
September 18th, 2013, 12:32 PM
With Exchange you have full control whether or not incoming emails will (better!) or will not include the text/plain part. With Office 365 you will need to contact Microsoft to discuss this.

racassel
September 18th, 2013, 02:00 PM
Here's the answer:
By default, 0ffice 365 pop mime retrieval format is set to “BestBodyType”
In order for CommitCRM to process the email correctly it needs to be reset to Mime type 2, HtmlAndTextAlternative.
This will allow you to see the text in the history section and not have to click on “Show Original Message”

Connect to 0365 with Powershell
1. $LiveCred = Get-Credential
2. Enter your admin login to 0365
(You can copy and paste the following three commands or type them one at a time and press enter)
3. $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.outlook.com/powershell/ -Credential $LiveCred -Authentication Basic –AllowRedirection
Import-PSSession $Session
4. Press Enter
5. List the current mailboxes
get-casmailbox *your mailbox here* | fl *pop*
Here is the result of the above command
ExternalPopSettings :
InternalPopSettings :
PopEnabled : True
PopUseProtocolDefaults : True
PopMessagesRetrievalMimeFormat : BestBodyFormat
PopEnableExactRFC822Size : False
PopSuppressReadReceipt : False
PopForceICalForCalendarRetrievalOption : False
6. set-casmailbox "your mailbox here - support@yourcompany.com" -PopMessagesRetrievalMimeFormat 2
7. Now run the command to list the settings to confirm everything worked
8. get-casmailbox support | fl *pop*
9.
10. ExternalPopSettings :
11. InternalPopSettings :
12. PopEnabled : True
13. PopUseProtocolDefaults : True
14. PopMessagesRetrievalMimeFormat : HtmlAndTextAlternative
15. PopEnableExactRFC822Size : False
16. PopSuppressReadReceipt : False
17. PopForceICalForCalendarRetrievalOption : False

Notice that the PopMessageRetrievalMimeFormat has changed to HtmlAndTextAlternative

Below are the other types of MIME types available.

Type: Description
0: TextOnly
1: HtmlOnly
2: HtmlAndTextAlternative
3: TextEnrichedOnly
4: TextEnrichedAndTextAlternative
5: BestBodyFormat
6: Tnef

racassel
October 14th, 2013, 10:12 AM
Update: This fixes the problem of receiving Exchange TNEF encoded (Exchange Default) messages into CommitCRM from Outlook users. We learned our 0365 Exchange / Outlook account was sending in TNEF format. This resulted in our replies not being displayed the CommitCRM history tab.

(< The textual email content cannot be displayed. No text/plain section found. Use the ‘Show Original’ option to view the message in your email client application >)

The fix is to log into 0365 with powershell and run the following command:
Set-RemoteDomain Default -TNEFEnabled $false

Now we can read our own replies in CommitCRM.

Reference:
http://help.outlook.com/en-us/140/gg263346.aspx#DisableAllTNEF

racassel
October 14th, 2013, 10:14 AM
Note: Maybe a CommitCRM upgrade will inclued the ability for the Email Connector to interpet and convert TNEF formatted messages (winmail.dat attachment issue) into readable emails as many clients and computer service companies are using Exchange.

Support Team
October 14th, 2013, 10:19 AM
Thank you for sharing this with the community and for the suggestion.

gregpattyn
September 20th, 2016, 09:33 AM
I get an error when I run the command in number 3 above.