Email Listener: Supported Incoming Email Content Types
PeteHalbeisen 060001VQWA Visits (14681)
All email messages have or should have a content-type header field which will determine how that email is handled. The Email Listener is not a true, full service email client and is therefore not as flexible and forgiving as email clients [such as Notes & Outlook] in handling the full range of email formats. The purpose of this article is to set the expectations for what content-types the listener will process. Note that the content-type type attribute of an email is distinct from character set which denotes how text for various languages is encoded.
text/plain The email message body is composed using basic text.
Examples: application/*, audio/*, image/*, video/*, etc.
While some email clients may recognize these as attachments, as stated, the listener is not a true, full service email client.
To send an attachment into the Email Listener, it must be as the attachment part of a multiple part email message.
An Aside About Properties
There are two System Properties related to email content processing. The are mxe.
For plain text handling message bodies that are written to a rich text field, please see: A Ma