Can an Exchange Shared Mailbox Store and Send All Email as Plain Text?
Question details
The user needs every message in an Exchange shared mailbox to be stored and delivered as plain text so an external SCADA system can retrieve and process it through POP3.
- Product
- Microsoft Exchange shared mailbox, Microsoft Outlook, and an external SCADA POP3 client
- Device & OS
- not provided
- Scenario
- An external SCADA system retrieves shared-mailbox messages through POP3 but cannot process HTML or rich-text email.
- Observed behavior
- Replies can arrive in rich-text format even when the original message was plain text. The user needs a way to ensure all retrieved messages are compatible with the SCADA client.
Check the SCADA client's documentation for support for MIME multipart messages, text/html bodies, and Outlook rich-text/TNEF content. Identify whether incoming mail passes through a gateway that can convert message bodies before delivery to the shared mailbox.
Convert unsupported messages before they reach the SCADA mailbox
Use this approach when every POP3-retrieved message must be readable by a plain-text-only client.
Outlook's plain-text reading setting changes how messages appear in Outlook; it does not convert the messages stored in Exchange or control what an external POP3 client downloads. There is no Outlook setting that enforces plain-text storage for every message in a shared mailbox.
A reliable solution requires a supported mail gateway or preprocessing service that converts messages before delivery, or a SCADA client that can extract plain-text content from the incoming message format.
Use the SCADA client's raw-message export or a mail administrator's diagnostic tools to inspect a failing POP3 message. Check for text/html, multipart/alternative, or application/ms-tnef content, including a winmail.dat attachment.
Open the email gateway's administration console and review its message-processing or content-conversion features. Ask the gateway vendor whether it can produce a text/plain body and handle rich-text/TNEF content for messages addressed to the SCADA mailbox.
If supported, create a recipient-specific processing rule for the shared mailbox. Convert the body to plain text before mailbox delivery and define how attachments, character encoding, and unsupported content should be handled.
Send plain-text, HTML, and Outlook rich-text test messages to the shared mailbox, including replies and messages with attachments. Retrieve them through the SCADA client and confirm that it can parse each resulting message.
Set Outlook to compose and display messages in plain text
Use these settings for messages written or viewed in classic Outlook for Windows, not to enforce the format of all POP3 downloads.
Use WPS Office for documents alongside your SCADA email workflow
WPS Office does not convert Exchange mailbox messages or fix SCADA POP3 parsing. For related documents, spreadsheets, and presentations, it offers a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility for straightforward migration.
Frequently Asked Questions
Does Outlook's plain-text reading option change what the SCADA system downloads?
No. File > Options > Trust Center > Trust Center Settings > Email Security changes how classic Outlook displays messages. It does not rewrite Exchange mailbox content or force POP3 retrieval to return a plain-text-only body.
Why can a reply to a plain-text message arrive as HTML or rich text?
The sender's email client determines the outgoing reply format and may change it. In classic Outlook, the sender can open the reply and choose Format Text > Plain Text, but this cannot control replies from all external senders.
Can POP3 itself convert HTML messages into plain text?
POP3 is a message-retrieval protocol, not a body-conversion tool. Check the SCADA client's settings or ask its vendor whether it can select a text/plain MIME part or convert HTML. If it cannot, conversion must happen before the client retrieves the message.
Is disabling Outlook rich text enough for a plain-text-only SCADA client?
Not necessarily. Removing rich-text/TNEF formatting does not guarantee a plain-text body because a message may still contain HTML or multipart MIME content. Test both HTML and rich-text messages through the actual SCADA POP3 client.
Will plain-text conversion preserve attachments and signed messages?
That depends on the conversion service. Plain-text bodies lose visual formatting, attachments need separate handling, and rewriting signed content can invalidate its signature. Review the gateway's conversion options and test these message types before enabling the rule for production mail.
