# Email reply includes inline styles with "incoming email prefer html" site setting on

**URL:** <https://meta.discourse.org/t/email-reply-includes-inline-styles-with-incoming-email-prefer-html-site-setting-on/61639>\
**Category:** Product Support\
**Created:** [26 april 2017 om 13:33 UTC](https://meta.discourse.org/t/email-reply-includes-inline-styles-with-incoming-email-prefer-html-site-setting-on/61639 "2017-04-26T13:33:20Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [27 april 2017 om 04:59 UTC](https://meta.discourse.org/t/email-reply-includes-inline-styles-with-incoming-email-prefer-html-site-setting-on/61639/8 "2017-04-27T04:59:54Z")

</div>

The setting `incoming_email_prefer_html` has already existed for a year, this commit removes it.

I agree that this late in the game it probably does not make sense to switch everyone to the new converter, it is guaranteed to have edge cases, but stripping a “site setting” just cause we fixed the implementation of the “site setting” does not really make sense to me.

Instead if we feel this has too much risk just revert the commit for now. Or leave the setting and mark in (experimental)

---

_[View the full topic](https://meta.discourse.org/t/email-reply-includes-inline-styles-with-incoming-email-prefer-html-site-setting-on/61639)._
