# MailChimp mirror 'eats' the mail

**URL:** https://meta.discourse.org/t/mailchimp-mirror-eats-the-mail/279296
**Category:** Support
**Created:** [September 17, 2023, 2:16pm UTC](https://meta.discourse.org/t/mailchimp-mirror-eats-the-mail/279296 "2023-09-17T14:16:37Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [September 17, 2023, 2:16pm UTC](https://meta.discourse.org/t/mailchimp-mirror-eats-the-mail/279296/1 "2023-09-17T14:16:37Z")

</div>

Continuing the discussion from [Create a read-only mailing list mirror](https://meta.discourse.org/t/create-a-read-only-mailing-list-mirror/77990):

I found an occurrence of a parsing error that I think may be useful to fix since it concerns MailChimp. Here is the problem:

### Issue

When I receive a multi-part MIME message newsletter, instead of having the HTML version displayed, I get a blank message.

The MIME delimiter might be the culprit, although I see no reason why the Mail class would choke on that:

```plaintext
This is a multi-part message in MIME format

--_----------=_MCPart_1956872529
Content-Type: text/plain; charset="utf-8"; format="fixed"
Content-Transfer-Encoding: quoted-printable

```

Here you can see that the multi-part message delimiter starts with `--` which is the usual marker for signature, that Discourse _may_ interpret as “stop parsing this, we’re done here”. I _guess_ this is why the resulting post is blank instead of showing the HTML part of the newsletter. But it sounds too crazy to be true.

The first topic post is correctly constructed, with the envelope icon that goes to the raw, text, and HTML parts. But the resulting post is wrong. Copy-pasting the HTML version into the first post fixes the issue, but obviously there’s something wrong in the rendering.

---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [September 17, 2023, 4:19pm UTC](https://meta.discourse.org/t/mailchimp-mirror-eats-the-mail/279296/2 "2023-09-17T16:19:26Z")

</div>

Have you tried changing the `incoming mail prefers HTML` setting and see if it makes any difference?

---

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [September 17, 2023, 4:25pm UTC](https://meta.discourse.org/t/mailchimp-mirror-eats-the-mail/279296/3 "2023-09-17T16:25:01Z")

</div>

Hi Richard! No, it’s already checked:

 ![image](https://global.discourse-cdn.com/meta/original/4X/a/5/3/a53bcb28381a961479ea5224e8b0f9fe60771951.png)

Maybe the `trim_incoming_emails` setting is doing something wrong.

---

<div class="post-metadata">

### Author: ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [September 17, 2023, 4:34pm UTC](https://meta.discourse.org/t/mailchimp-mirror-eats-the-mail/279296/4 "2023-09-17T16:34:05Z")

</div>

If it’s turned on, try turning it off.  
And yes, the trim setting would be a good second possible culprit.

---

<div class="post-metadata">

### Author: ![hellekin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hellekin/32/51636_2.png) [@hellekin](https://meta.discourse.org/u/hellekin)
#### Post date: [October 1, 2023, 11:33am UTC](https://meta.discourse.org/t/mailchimp-mirror-eats-the-mail/279296/5 "2023-10-01T11:33:10Z")

</div>

After removing both `incoming email prefer html` and `trim incoming email`, and rebuilding the post’s HTML, nothing happened. I will leave the settings like this and wait for next incoming email (about two weeks) and see what happens then.
