Exchange 2007 Text conversion

Hello all,

My company wants to set a policy to force all incoming email to be converted to plain text. I have already set the organization configuration/hub transport / remote domains to Never use Excahnge Rich Text. I also have installed the oultook12.adm template and set the option to use just plain text. This works however the end user can still click on the options tab and press the HTML format button and send in html.
How can I force html to be converted to plain text for all incoming email?

How can i force all users to send with plain text?

Thank you for your reply.
Who is Participating?
mark1208Connect With a Mentor Commented:
Hi kwoznica,

You were absolutely on the right track with using the Outlk12.adm template to restrict these options from the client side. You just didn't go far enough!  :)

Loosely follow the instructions outlined in kb930508, since they were written for OL2003. Pay special attention to the Step 3: Modify the Group Policy object section. Based on your post, you've likely already completed Step 3.6. You just need to continue with the all-important Step 3.10 to disable the HTML and Rich Text check boxes within the Ribbon UI.

You may want to also verify that Step 3.2 translates successfully  from (Tools > Options > Preferences tab > E-mail Options... > "Read all standard mail in plain text") in OL2003 to (Tools > Trust Center... > E-mail Security > "Read all standard mail in plain text") in OL2007.

Based this "fun" set of documents, following are the Control IDs that correspond to the options to be disabled:
5564 = HTML (see OutlookMailComposeItemRibbonControls.xlsx)
5565 = Rich Text (see OutlookMailComposeItemRibbonControls.xlsx)
9087 = ??? (present in kb930508 but not in any of the docs for OL2007)
9088 = ???
Other Links:
1) Lists of Control IDs for Office 2007:
2) TechNet info on disabling user interface items:
3) VBA for locating Command Bar IDs (but you won't find 9087 or 9088 here!):
4) Builtin Control Scanner (also searches for control IDs, but was unable to locate 9087 or 9088):

My extensive scouring of the InterWeb hasn't turned up anything related to the two  elusive  control ID's (argh!), though I'll keep looking.

In the meantime, I hope this helps!
Not really recommended, general thumb rule should be reply in same format as received.
Still refer:
Nitin Gupta (gupnit)
Hi kwoznica, have you had a chance to test the recommendation(s) outlined above? Just wanted to follow up to see if/how things were progressing.

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Any update?
Just following up to see if/how things are progressing on this issue ... any update/feedback?

kwoznicaAuthor Commented:
Yes this was very helpful. I implemented the solution via group policy and it worked quite well. Our sales team backlashed and I had spin them into a different organizational unit.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.