Menu icon Foundation

My Posts


My Comments

Tony Strack commented on Tony Strack's post 2 months

Dimitar...You just made my day. That worked. Thank you!

Tony Strack commented on Tony Strack's post 10 months

No. However, I have narrowed it down to the inliner that the CMS (HubSpot) uses. HubSpot wraps any styles in the <head> in a <div> with an ID that takes care of the inlining on the backend.
If I remove the ID from that div, essentially eliminating the inlining process, the email renders fine in Thunderbird.
But I need the utilize inlining for email clients that require it, such as Gmail. It works perfectly fine for those email clients when inlined.
At this point, I'm just not supporting Thunderbird, but would love a solution if anyone has one.

Tony Strack commented on Tony Strack's post 11 months

I believe that the Thunderbird email client itself is stripping out the doctype. Certain email clients do this: https://www.emailonacid.com/blog/article/email-development/doctype_-_the_black_sheep_of_html_email_design
Another thing I noticed while troubleshooting is that my email CMS (HubSpot) uses an ID to inline styles. This is done so that it works for email clients that don't support <style> in the head: https://www.campaignmonitor.com/css/style-element/style-in-head/
When I take out the inline functionality, the email renders correctly in Thunderbird. But in turn, no longer renders correctly in those email clients that don't support <style> in the head.
I'm getting closer to a solution based on those two findings, but still not quite ther

Tony Strack commented on Tony Strack's post 11 months

I believe that the Thunderbird email client itself is stripping out the doctype. Certain email clients do this: https://www.emailonacid.com/blog/article/email-development/doctype_-_the_black_sheep_of_html_email_design
Another thing I noticed while troubleshooting is that my email CMS (HubSpot) uses an ID to inline styles. This is done so that it works for email clients that don't support <style> in the head: https://www.campaignmonitor.com/css/style-element/style-in-head/
When I take out the inline functionality, the email renders correctly in Thunderbird. But in turn, no longer renders correctly in those email clients that don't support <style> in the head.
I'm getting closer to a solution based on those two findings, but still not quite there.
 

Tony Strack commented on Tony Strack's post 12 months

So I figured out that Thunderbird strips out the Doctype. I loaded my HTML into Firefox and it rendered correctly, but once I stripped out the Doctype, it rendered like the screenshot above.
Is there a way to force the Doctype? Or use a specific one? Currently I'm using: 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

Posts Followed

No Content

Following

    No Content

Followers

My Posts


My Comments

You commented on Tony Strack's post 2 months

Dimitar...You just made my day. That worked. Thank you!

You commented on Tony Strack's post 10 months

No. However, I have narrowed it down to the inliner that the CMS (HubSpot) uses. HubSpot wraps any styles in the <head> in a <div> with an ID that takes care of the inlining on the backend.
If I remove the ID from that div, essentially eliminating the inlining process, the email renders fine in Thunderbird.
But I need the utilize inlining for email clients that require it, such as Gmail. It works perfectly fine for those email clients when inlined.
At this point, I'm just not supporting Thunderbird, but would love a solution if anyone has one.

You commented on Tony Strack's post 11 months

I believe that the Thunderbird email client itself is stripping out the doctype. Certain email clients do this: https://www.emailonacid.com/blog/article/email-development/doctype_-_the_black_sheep_of_html_email_design
Another thing I noticed while troubleshooting is that my email CMS (HubSpot) uses an ID to inline styles. This is done so that it works for email clients that don't support <style> in the head: https://www.campaignmonitor.com/css/style-element/style-in-head/
When I take out the inline functionality, the email renders correctly in Thunderbird. But in turn, no longer renders correctly in those email clients that don't support <style> in the head.
I'm getting closer to a solution based on those two findings, but still not quite ther

You commented on Tony Strack's post 11 months

I believe that the Thunderbird email client itself is stripping out the doctype. Certain email clients do this: https://www.emailonacid.com/blog/article/email-development/doctype_-_the_black_sheep_of_html_email_design
Another thing I noticed while troubleshooting is that my email CMS (HubSpot) uses an ID to inline styles. This is done so that it works for email clients that don't support <style> in the head: https://www.campaignmonitor.com/css/style-element/style-in-head/
When I take out the inline functionality, the email renders correctly in Thunderbird. But in turn, no longer renders correctly in those email clients that don't support <style> in the head.
I'm getting closer to a solution based on those two findings, but still not quite there.
 

You commented on Tony Strack's post 12 months

So I figured out that Thunderbird strips out the Doctype. I loaded my HTML into Firefox and it rendered correctly, but once I stripped out the Doctype, it rendered like the screenshot above.
Is there a way to force the Doctype? Or use a specific one? Currently I'm using: 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

Posts Followed

No Content

Following

  • No Content

Followers

  • No Content