We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Auto email response keeps adding this: This is a multi-part message in MIME format. --------------8ACDCD9F2CDB3AD82EFC10CC Content-Type: text/html; charset=utf-

  • 2 回覆
  • 2 有這個問題
  • 2 次檢視
  • 最近回覆由 jobe77x

more options

Hi Everyone,

Have been trying to set up an automatic email response and the set up is fine, but the reply message keeps putting this text at the beginning of the message: This is a multi-part message in MIME format. --------------8ACDCD9F2CDB3AD82EFC10CC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit.

Any ideas how to get rid of this?

I have also tried not sending it in HTML and the whole message comes back unreadable.

Hi Everyone, Have been trying to set up an automatic email response and the set up is fine, but the reply message keeps putting this text at the beginning of the message: This is a multi-part message in MIME format. --------------8ACDCD9F2CDB3AD82EFC10CC Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit. Any ideas how to get rid of this? I have also tried not sending it in HTML and the whole message comes back unreadable.

所有回覆 (2)

more options

is your automatic response set to fire after classification? Junk classification requires the message body, otherwise your filter can fire before the body is fully downloaded with unpredictable results such as you see.

more options

Hi I'm blowing this question alive again, i have the the same issue:

This error occurs when the reply with template is used in a filter. when sending the template a normal message everything works fine. it seems like it's encoding of the image, doesn't work correctly when the reply with template function are doing it

instead this is in the beginning of the letter:


This is a multi-part message in MIME format. --------------E91443BF56E384366DCC25BB Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

and then the rest of the of the message looks like normal, and at the end of the message is the rest of the mime code:



E91443BF56E384366DCC25BB Content-Type: image/png; name="weare.png" Content-Transfer-Encoding: base64 Content-ID: Content-Disposition: inline; filename="weare.png" iVBORw0KGgoAAAA


.... and few hundred more lines of data..

this must be a bug?