When accessing an Exchange 2003 server via IMAP, emails that were sent as text/plain (and ones that had no MIME encoding specified at all) get automatically converted to multipart/alternative with the original text/plain body and a text/html body. This is … stupid. It doesn't even bother to specify a monospaced font.

The new MIME part starts like this:

Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =

<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>{{body}}

(All the "3D" stuff is quoted-printable encoding for an equals sign; there's nothing wrong on that front, surprisingly.)

How can I make this stop?


Gavin McTaggart responded to a similar question, albeit about Exchange 2007:

Have a look at this Technet document, specifically the ImapMessagesRetrievalMimeFormat switch. The documentation is exceedingly vague, but Exchange can force the format of the messages as they are retrieved from the server, either by user (as the link indicates) or on the service itself; in which case you would use the Set-ImapSettings command, and change the MessageRetrievalMimeFormat option.

I haven't had a chance to test it yet. I don't really have any notion that the Exchange Management Shell indirectly referenced exists or will function with Exchange 2003, though.

| improve this answer | |

Isn't this configured on the Message Format tab of the IMAP4 Virtual Server properties pages? I believe that sending the message in both Text and HTML formats is the default setting.

| improve this answer | |
  • I've played with that and it doesn't seem to actually have any effect at all. If you can refute that, please let me know. – wfaulk Apr 1 '10 at 23:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.