Troubleshooting Email Connector - Mule 4

mail.mime.decodetext.strict
Controls the decoding of MIME-encoded words. The MIME specification requires that encoded-words start at the beginning of a whitespace-separated word. Some mailers incorrectly include encoded-words in the middle of a word. If the mail.mime.decodetext.strict system property is set to false, an attempt is made to decode these illegal encoded-words. Defaults to true.

mail.mime.encodeeol.strict
Controls the choice of Content-Transfer-Encoding for MIME parts that are not of type text. Often these MIME parts contain textual data for which an encoding that allows the normal end of line conventions is appropriate. In rare cases, MIME parts that are not of type text appear to contain entirely textual data but they require an encoding that preserves CR and LF characters without change. If the mail.mime.encodeeol.strict system property is set to true,this type of encoding is used when necessary. Defaults to false.

mail.mime.charset
Specifies the default MIME charset to use for encoded words and text parts that don’t otherwise the property specify a charset. Usually, the default MIME charset is derived from the default Java charset, as specified in the file.encoding system property. Most applications do not need to explicitly set the default MIME charset. Set this property when the default MIME charset to use for mail messages is different than the charset used for files stored on the system.

mail.mime.ignoreunknownencoding
Controls whether unknown values in the Content-Transfer-Encoding header, as passed to the decode method, cause an exception. If set to true, unknown values are ignored and 8bit encoding is assumed. Otherwise, unknown values throw a MessagingException exception.

mail.mime.multipart.ignoremissingendboundary
Set this property to false to throw a MessagingException exception if the multipart data does not end with the required end boundary line. If this property is set to true or not set at all, missing end boundaries are not considered an error, and the final body part ends at the end of the data.

mail.mime.multipart.ignoremissingboundaryparameter+ Set this property to false to throw a MessagingException exception if the Content-Type of the MIME multipart does not include a boundary parameter. If this property is set to true or not set at all, the multipart parsing code searches for a line that looks like a boundary line and uses that line as the boundary separating the parts.

mail.mime.multipart.ignoreexistingboundaryparameter
Set this property to true to ignore any boundary and instead search for a boundary line in the message as with the mail.mime.multipart.ignoremissingboundaryparameter system property.

mail.mime.multipart.allowempty
Usually, when writing a MIME multipart that contains no body parts, or when trying to parse a multipart message with no body parts, a MessagingException exception is thrown. The MIME type specification does not allow multipart content with no body parts. Set the mail.mime.multipart.allowempty system property to true to override this behavior. When writing out such a MIME multipart, a single empty part is included. When reading such multipart, a MIME multipart is created with no body parts.