I work in an environment where some people are using Microsoft Exchange and some people are not. The meeting invitations sent out by Exchange include a text/calendar attachment with the meeting information in iCal format. They also include an empty text/plain and an empty text/html part.

Is there any way to configure Exchange such that it will populate either (or both!) the text/plain or the text/html part with a human-readable version of the meeting summary? This would help out people using mail clients that do not have native support for text/calendar attachments.

  • 4
    What a novel concept, catering to those of us who may be reading email on a terminal. +1 for "Can we make Microsoft play nice with others?" sentiment. – voretaq7 Apr 10 '12 at 16:53
  • Dude. I wonder if there's a way to ante in on a bounty for this bad boy. See how far up we can drive a bounty if a bunch of people can pitch in. =) – Magellan Apr 10 '12 at 18:23
  • I do not believe what you're asking for is possible. – Tatas Apr 10 '12 at 18:56
  • What (major) version of Exchange? What actual clients are people running? If the Exchange folks are running Outlook, it might be possible to write a client-side mod to cause/fix the extra attachment. It might be possible to write something deeper that handles it for the entire Exchange server but that would be pretty involved. – Mark Allen Apr 20 '12 at 0:32
  • 1
    Actually, I'd like to see a general answer to this one. – Magellan May 17 '12 at 16:01

Yes, you can do this, but the first way I am suggesting may be a crude hack.

Add transport rules that parse the meeting summary and add it to a disclaimer (temporarily), then use this same disclaimer as an addition to each message. As Exchange will add the disclaimer with a matching format, you can output it in an HTML and text friendly manner simultaneously via use of or other similar tags. HTML is not unreadable either.

An alternative way may be to create a mailbox that receives ALL meeting invites and then replies to a specific number of clients on the to/cc/etc with a text version of the same if they match a list of text-preferential users.

  • this. Native exchange doesn't have any in-built support for changing outgoing messages. third-party (proprietary) tools exist, but with native exchange all you can do is append a disclaimer – acolyte May 24 '12 at 13:11

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.