Mime Configuration

The bean accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the bean, access to these internal properties is provided through the Config method.

MIME Configuration Settings


	FoldHeaders: Tells the bean whether to fold the headers. If true, the bean will fold the headers if the headers are over a certain length. If false, the headers will be on one line regardless of length.
	IncludeHeaders: Tells the bean whether to include the headers when encoding the message. If true, the bean will include the headers when EncodeToFile or EncodeToString are called. If false, only the message will be encoded. The default value for IncludeHeaders is false.
	MaxParts: The maximum number of parts to be parsed from a mime message. This config should be set to limit the amount of parts that will be parsed by the component and saved into the collection . By default, this value is 100. Therefore up to 100 parts will be parsed from a mime message by default.
	RequireVersionHeader: Specifies whether or not the bean should require the version header. If true, the bean will require that the "MIME-Version" header be included in the MessageHeaders. If the header is not present during decoding, the component throws an exception. This config is false by default.
	SanitizeFilename: Whether invalid characters are replaced in MIME part filenames. If True, the bean will replace invalid characters with an underscore when decoding the MIME message. This applies to the filename held in the Filename field. When True the following characters are considered invalid: \ / " : ? * < > \| Any characters with ASCII values between 0-31 are also considered invalid. The default value is False.
	TempFilePath: If set, the temporary files created during MIME decoding and encoding will be put in the path specified. The TempFilePath property sets the path at which the temporary files will be created.

Base Configuration Settings

GUIAvailable: Tells the bean whether or not a message loop is available for processing events.

In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The bean will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation.

In some non-GUI applications an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GuiAvailable to false will ensure that the bean does not attempt to process external events.

UseDaemonThreads: Whether threads created by the bean are daemon threads.

If set to True, when the bean creates a thread the thread's Daemon property will be explicitly set to True. By default this setting is False and the bean will not set the Daemon property on the created thread.