# URLs being dropped from Thunderbird-generated replies

**URL:** https://meta.discourse.org/t/urls-being-dropped-from-thunderbird-generated-replies/163751
**Category:** Support
**Created:** [September 11, 2020, 4:39pm UTC](https://meta.discourse.org/t/urls-being-dropped-from-thunderbird-generated-replies/163751 "2020-09-11T16:39:32Z")
**Posts on this page:** 1
**Showing post:** 24

<div class="post-metadata">

### Author: ![bsoares](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bsoares/32/231482_2.png) [@bsoares](https://meta.discourse.org/u/bsoares)
#### Post date: [October 4, 2021, 2:32pm UTC](https://meta.discourse.org/t/urls-being-dropped-from-thunderbird-generated-replies/163751/24 "2021-10-04T14:32:22Z")

</div>

Hmmm, in that example, and in the full email source you messaged me (thank you!) the `moz-do-not-send` attribute should not affect the display of the `<img>` or `<a>` tags that that attribute appears in. The mozfilter is only looking at values in the `class` attribute, and I can’t immediately see anywhere else that it might get filtered.

As such I can’t work out why the link-with-alias’s content and href get separated out, unless for some reason the discourse importer is suddenly deciding to use the plain/text part of the Mime encoded email (which does have the text and URL separated). Why it would do that I don’t know.

In your test discourse setup can you try importing/emailing a thunderbird HTML email with both a link-with-alias and, say an embedded image or something else that will mark it out as the HTML part of the email?

---

_[View the full topic](https://meta.discourse.org/t/urls-being-dropped-from-thunderbird-generated-replies/163751)._
