Issue:
The HTML content of the inbound email is formatted properly, but after it is converted into a case by Email-to-Case, all the formatting is lost in the description section (meant to align with the format of the content in the inbound HTML email).
A common cause is missing HTML tags in the inbound HTML email. For example, there may be a closing tag </p> for a paragraph but missing the opening tag <p> or there may be a closing tag </br> but missing the opening tag <br>.
The inbound HTML email might open correctly in a web browser as a normal HTML page, but this does not mean that it is written properly without any missing HTML tags. Usually, a web browser has a certain tolerance for dealing with missing HTML tags, but in Salesforce, the best practice is to ensure that the HTML code is properly written without any missing tags. Otherwise, unexpected behavior may occur.
If any missing tags are found in the inbound HTML email, create a new copy of the email, restore all the missing tags, and conduct a test to confirm if the formatting issue can be resolved.
000386050

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.