# Inline Image post via Thunderbird not processed properly

**URL:** https://meta.discourse.org/t/inline-image-post-via-thunderbird-not-processed-properly/94961
**Category:** Bug
**Created:** [8월 17, 2018, 4:36오전 UTC](https://meta.discourse.org/t/inline-image-post-via-thunderbird-not-processed-properly/94961 "2018-08-17T04:36:27Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![LeoMcA](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/leomca/32/87233_2.png) [@LeoMcA](https://meta.discourse.org/u/LeoMcA)
#### Post date: [8월 17, 2018, 2:19오후 UTC](https://meta.discourse.org/t/inline-image-post-via-thunderbird-not-processed-properly/94961/6 "2018-08-17T14:19:48Z")

</div>

A-ha, I’ve seen this a few times with Thunderbird (but never with images, just with text so it didn’t really impact the usability/readability of the email).

I _imagine_ what’s going on here is that somewhere in the HTML → Markdown conversion some whitespace is being added (or not removed) producing something like this:

```plaintext
    <img blah blah blah blah>

```

which is rendered like so:

```
<img blah blah blah blah>

```

Getting the raw markdown output of the post will confirm this. Do that by replacing the `/t/<slug>/` part of the url with `/raw/`, eg:

`https://meta.discourse.org/t/inline-image-post-via-thunderbird-not-processed-properly/94961/5` → [`https://meta.discourse.org/raw/94961/5`](https://meta.discourse.org/raw/94961/5)

---

_[View the full topic](https://meta.discourse.org/t/inline-image-post-via-thunderbird-not-processed-properly/94961)._