SOLVED

Re: Microsoft Office 365 Outlook rendering poorly

Go to solution
jrent
Level 2

Microsoft Office 365 Outlook rendering poorly

Just yesterday we received user feedback that our emails are rendering poorly in specifically Office 365 Outlook when accessed through any web browser. Outlook desktop apps are fine as well as every other email client. See image below and this Litmus link – https://litmus.com/pub/ELkgO7uottua7X0R – where you can see that the very last 2 items under "Web-based clients" are Office 365 Outlook and the only 2 results that display this way.

  • Any ideas if there have been recent changes to Office 365 Outlook that would cause this?
  • Has any one remediated these sorts of bugs within their email templates?

Screenshot 2024-06-25 at 8.26.05 PM.png

1 ACCEPTED SOLUTION

Accepted Solutions
jrent
Level 2

Re: Microsoft Office 365 Outlook rendering poorly

As of yesterday (06/27/2024) our blue link and spacing issues seem to "magically" be resolved in Office 365 Outlook. I had not implemented any template changes yet, so this indicates to me that some changes were made on the Microsoft product side. Yay!

 

This morning I realized that the issue with our logos not displaying in the header and footer of the template is due to the fact that the src for these was http://.... instead of https://.... – the secure protocol is what Office 365 Outlook wants.

 

So, our issues are solved! For now...

 

Thanks for the input.

View solution in original post

9 REPLIES 9
ktronolone
Level 3

Re: Microsoft Office 365 Outlook rendering poorly

We did encounter problems with renderings in a few versions of Outlook this week (online and desktop.) Our team dev found that styles are being removed from the head so classes had to be applied to the elements in the body. This was our issue, perhaps it affected your template as well. Best of luck with a solve!

jrent
Level 2

Re: Microsoft Office 365 Outlook rendering poorly

Thank you @ktronolone!

 

Following up as I continue to troubleshoot...We use Marketo with FeedOtter. I've been emailing with their support to see if they had any info. They provided me with a response as well as this insight from their rep at Litmus:

 

Your issue in Office 365 you described sound similar to odd behaviors our own email team is seeing in Microsoft webmail clients as well. There is a thread on this in the Email Geeks slack community if you have joined there (or want to!).

It appears Microsoft is rolling out some UI changes that are randomly breaking or removing style tags and impacting the CSS so things like fonts and spacing are messed up. Some people are seeing images being affected as well. Reloading with F5 has helped some people get to a more stable version but other people are still seeing different errors.

A person on that thread found a workaround that may help:
"Since it's only pulling the content within body tags, try adding a <body></body> tag around your <style></style> tag in the head so you end up with two in the code."

At this point, it seems we're a bit stuck until Microsoft's teams get things settled. Our teams try to keep up with what these external services are doing and maybe even get ahead of it but we're in the same boat with you for now. Hopefully they will figure this out soon!

In testing, adding a <body> tag around your template's <style> tag does resolve the CSS problems. Weeeiiiiird.

My last issue to resolve at the moment is why my logo images aren't displaying at the top and bottom of our emails.

ktronolone
Level 3

Re: Microsoft Office 365 Outlook rendering poorly

Sheesh! That is frustrating. Thank you for sharing as you are working through your issues. I'm positive this will help some other folks. 

SanfordWhiteman
Level 10 - Community Moderator

Re: Microsoft Office 365 Outlook rendering poorly

The problem with this “workaround” is you’ve then created badly broken HTML. And classic spam software (e.g. SpamAssassin) treats non-compliant HTML as one of the markers of spam.

jrent
Level 2

Re: Microsoft Office 365 Outlook rendering poorly

@SanfordWhiteman Ya. I was wondering about that. Having 2 <body> tags in the document is invalid HTML but I wasn't sure what the repercussions of that would be. Thanks for the spam flag.

 

Another solution for the link styles that seems to be working is if I just put !important styles directly, inline on every <a> tag. More labor there but maybe a safer way to go about it. Can't do :hover and :focus styles that way but at least it will display properly otherwise.

 

Danielle_Wong
Level 8 - Community Advisor

Re: Microsoft Office 365 Outlook rendering poorly

would copying the entire style section and pasting it in the body be a spam trigger?

SanfordWhiteman
Level 10 - Community Moderator

Re: Microsoft Office 365 Outlook rendering poorly

Wouldn’t expect so because while that’s technically invalid HTML as well (<style> must be inside <head> in the spec), that rule is broken throughout the web. 

 

In contrast, breaking fundamentals like where <body> goes and having more than one <body> is the kind of thing that’s long been a sign of a poorly designed user-agent, i.e. one more likely to send spam.

Dave_Roberts
Level 10

Re: Microsoft Office 365 Outlook rendering poorly

Here's a look at the support chart for the <style> element in email:

Dave_Roberts_0-1719935187428.png

Notice the Notes section #3:  Buggy. The first <head> in the HTML is removed, so <style> elements need to be in a second <head> element.

As Sanford pointed out, this isn't exactly best practice and at best it's invalid HTML. 

https://www.caniemail.com/features/html-style/

 

jrent
Level 2

Re: Microsoft Office 365 Outlook rendering poorly

As of yesterday (06/27/2024) our blue link and spacing issues seem to "magically" be resolved in Office 365 Outlook. I had not implemented any template changes yet, so this indicates to me that some changes were made on the Microsoft product side. Yay!

 

This morning I realized that the issue with our logos not displaying in the header and footer of the template is due to the fact that the src for these was http://.... instead of https://.... – the secure protocol is what Office 365 Outlook wants.

 

So, our issues are solved! For now...

 

Thanks for the input.