# Mailing list mode: "Upload" links broken (?) in e-mails

**URL:** <https://meta.discourse.org/t/mailing-list-mode-upload-links-broken-in-e-mails/112354>\
**Category:** Bug\
**Created:** [March 22, 2019, 5:50pm UTC](https://meta.discourse.org/t/mailing-list-mode-upload-links-broken-in-e-mails/112354 "2019-03-22T17:50:38Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [March 24, 2019, 11:45pm UTC](https://meta.discourse.org/t/mailing-list-mode-upload-links-broken-in-e-mails/112354/3 "2019-03-24T23:45:46Z")

</div>

This is a very interesting problem.

At the moment we simply ship the `raw` markdown to the `plaintext` section of emails.

We made that decision many years ago and were kind of aware of some of the cracks.

@eviltrout / @codinghorror how do you feel about changing the mailer so it does `HTML` =\> `text` and uses that for the text part of the MIME vs using Post `raw`?

We now have a very robust patterns for doing `HTML` =\> `text` living inside Discourse and could make a custom one here. It is a pretty big job though cause we would have to be ultra careful with quotes and oneboxes.

For example now text contents has stuff like:

```plaintext
[quote="codinghorror, post:2, topic:112354"]
this is definitely a bug
[/quote]

```

This would probably be a nicer way of rendering this in a text email.

```plaintext
> this is definitely a bug
URL-TO-QUOTE

```

---

_[View the full topic](https://meta.discourse.org/t/mailing-list-mode-upload-links-broken-in-e-mails/112354)._
