Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

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

  • 2 replies
  • 2 have this problem
  • 2 views
  • Last reply by 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.

All Replies (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?