MIME Component

Properties   Methods   Events   Config Settings   Errors  

The MIME component allows for the simple encoding and decoding of MIME structures, such as message attachments and file uploads.

Syntax

IPWorks.Mime

Remarks

The component may be used for decoding or encoding of messages. Message holds the content of the encoded message or the filename that holds the encoded data. The decoded data are provided in Parts collection.

To decode a MIME message, you should first assign either the whole message (headers and body) to Message or put the message headers into the MessageHeaders property and the message body or the filename holding it into the Message property. Calling DecodeFromFile or DecodeFromString directs the component to start parsing the message: it will fill out the ContentType and ContentTypeAttr properties with message content-type information, and it will enter information about message parts into the Parts collection, which includes part sizes, part content types, part content type attributes, part content disposition, part content disposition attributes, part encoding, part name, part filename, part headers, or part content (part-decoded string or part-decoded file) for each decoded part.

Calling the DecodeFromString or DecodeFromFile to decode does not actually decode the message but only parses it. The real decoding is done when the part content in the Parts collection is first accessed.

To encode data into a MIME message, you should first assign values for each part to either a part-decoded string or a part- decoded file in the Parts collection property, and optionally assign values to the other part attributes in the Parts collection. Assigning a value to the part-decoded string or a part-decoded file through the Parts collection, fills out automatically the part headers into the Parts collection for the respective part. Calling EncodeToFile or EncodeToString directs the component to fill out the Message with the message body and the MessageHeaders with the headers.

The Progress event is fired as the message is parsed and the data are decoded/encoded.

Property List


The following is the full list of the properties of the component with short descriptions. Click on the links for further details.

BoundaryThis property includes the boundary separating the MIME parts. It has a maximum length of 80 bytes.
ContentTypeThis property includes the value of the content-type header of the message that was encoded/decoded.
ContentTypeAttrThis property includes the attributes of the content-type header of the message that was encoded or decoded.
MessageThis property contains the encoded message text or a path to a file that contains the encoded message text.
MessageHeadersThis property includes the headers of the MIME message.
MessageHeadersStringThis property includes the string version of the MIME message headers.
PartsThis property contains information about all parts of a MIME message.

Method List


The following is the full list of the methods of the component with short descriptions. Click on the links for further details.

configSets or retrieves a configuration setting.
decodeFromFileThis method decodes from a file.
decodeFromStreamThis method decodes from a stream.
decodeFromStringThis method decodes from a string.
decodePartThis method decodes the specified part.
decodePartToFileThis method decodes the specified part to a file on disk.
decodePartToStreamThis method decodes the specified part to a stream.
encodeToFileThis method encodes to a file.
encodeToStreamThis method encodes to a stream.
encodeToStringThis method encodes to a string.
resetReset the component.
resetDataThis method resets the values of all headers and part properties.

Event List


The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.

ErrorFired when information is available about errors during data delivery.
HeaderThis event is fired every time a header is parsed.
ProgressThis event shows the progress of decoding or encoding the input data.

Config Settings


The following is a list of config settings for the component with short descriptions. Click on the links for further details.

AlternateCharsetNamesMaps alternate charset names to the specified name.
FoldHeadersTells the component whether to fold the headers.
IncludeHeadersTells the component whether to include the headers when encoding the message.
MaxPartsThe maximum number of parts to be parsed from a mime message.
RequireVersionHeaderSpecifies whether or not the component should require the version header.
SanitizeFilenameWhether invalid characters are replaced in MIME part filenames.
TempFilePathIf set, the temporary files created during MIME decoding and encoding will be put in the path specified.
BuildInfoInformation about the product's build.
GUIAvailableWhether or not a message loop is available for processing events.
LicenseInfoInformation about the current license.
MaskSensitiveWhether sensitive data is masked in log messages.
UseDaemonThreadsWhether threads created by the component are daemon threads.
UseInternalSecurityAPIWhether or not to use the system security libraries or an internal implementation.

Boundary Property (MIME Component)

This property includes the boundary separating the MIME parts. It has a maximum length of 80 bytes.

Syntax


public String getBoundary();


public void setBoundary(String boundary);

Default Value

""

Remarks

This property contains the boundary separating the MIME parts and has a maximum length of 80 bytes. The component automatically generates a random boundary value during encoding, if no value is given. During decoding, this property is filled with the boundary from the actual MIME message.

The component will truncate any string longer than 80 bytes if assigned to Boundary.

ContentType Property (MIME Component)

This property includes the value of the content-type header of the message that was encoded/decoded.

Syntax


public String getContentType();


public void setContentType(String contentType);

Default Value

""

Remarks

This property contains the value of the content-type header of the message that was encoded/decoded. The component filters it out from the MessageHeaders. It shows the user information about the type of the parts and their relation to each other.

The content-type attributes, such as filename, boundary, and charset, are held in this property.

ContentTypeAttr Property (MIME Component)

This property includes the attributes of the content-type header of the message that was encoded or decoded.

Syntax


public String getContentTypeAttr();


public void setContentTypeAttr(String contentTypeAttr);

Default Value

""

Remarks

This property contains content-type attributes such as "filename", "boundary", and "charset".

Message Property (MIME Component)

This property contains the encoded message text or a path to a file that contains the encoded message text.

Syntax


public byte[] getMessage();


public void setMessage(byte[] message);

Default Value

""

Remarks

This property contains the encoded message text or a path to a file that contains the encoded message text. The component fills out this property with the message body and MessageHeaders during encoding. The user may assign both the headers and the body to this property and leave MessageHeaders empty before decoding.

This property is not available at design time.

MessageHeaders Property (MIME Component)

This property includes the headers of the MIME message.

Syntax


public HeaderList getMessageHeaders();


public void setMessageHeaders(HeaderList messageHeaders);

Remarks

This property contains the headers of the MIME message. The component fills out this property upon encoding. The user should use them as additional headers when emailing the Message.

During decoding, if this property is empty, the component will try to find the headers in the beginning of the Message and then will fill out this property accordingly.

Please refer to the Header type for a complete list of fields.

MessageHeadersString Property (MIME Component)

This property includes the string version of the MIME message headers.

Syntax


public String getMessageHeadersString();


public void setMessageHeadersString(String messageHeadersString);

Default Value

""

Remarks

The component fills out MessageHeadersString upon encoding. The user should use these strings as additional headers when emailing the Message.

This property contains a string version of the MIME message headers. During decoding, if this property is empty, the component will try to find the headers in the beginning of the Message and will fill out this property accordingly.

Parts Property (MIME Component)

This property contains information about all parts of a MIME message.

Syntax


public MIMEPartList getParts();


public void setParts(MIMEPartList parts);

Remarks

This property contains information about all parts of a MIME message. A MIME message consists of different parts, separated by either a user-specified or an auto-generated boundary. Each part has its own set of headers that are contained in the Headers field.

The MIMEPARTS collection is filled out by the component when a call to either DecodeFromFile or DecodeFromString is made. However, when the EncodeToFile or EncodeToString methods are called, the component encodes the data given in either DecodedFile or DecodedString into a MIME message.

This collection is indexed from 0 to size -1.

Please refer to the MIMEPart type for a complete list of fields.

Config Method (Mime Component)

Sets or retrieves a configuration setting.

Syntax

public String config(String configurationString);

Remarks

Config is a generic method available in every component. It is used to set and retrieve configuration settings for the component.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.

To set a configuration setting named PROPERTY, you must call Config("PROPERTY=VALUE"), where VALUE is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a configuration setting, you must call Config("PROPERTY"). The value will be returned as a string.

DecodeFromFile Method (Mime Component)

This method decodes from a file.

Syntax

public void decodeFromFile();

Remarks

This method decodes the data file given in Message and optionally MessageHeaders and fills out the Parts collection for each decoded part.

Example. Decoding from a File:

MIMEControl.Message = "C:\filename.txt" MIMEControl.DecodeFromFile

In this example, C:\filename.txt must contain the MIME headers and body. If not, the MessageHeaders property must be set to the appropriate MIME headers.

DecodeFromStream Method (Mime Component)

This method decodes from a stream.

Syntax

public void decodeFromStream(java.io.InputStream inputStream);

Remarks

This method decodes from a stream. It is the same as DecodeFromString, but now the MIME message is passed to this method as a stream.

This method decodes the data given by the InputStream and optionally MessageHeaders and fills out the Parts collection.

Example. Decoding a Mail Message:

MIMEControl.MessageHeaders.AddRange(MailControl.MessageHeaders) MIMEControl.DecodeFromStream(InputStream)

DecodeFromString Method (Mime Component)

This method decodes from a string.

Syntax

public void decodeFromString();

Remarks

This method decodes from a string. It is the same as DecodeFromFile, but now the Message denotes the real encoded message rather than a filename.

This method decodes the data given in Message and optionally MessageHeaders and fills out the Parts collection.

Example. Decoding a Mail Message:

MIMEControl.MessageHeaders.AddRange(MailControl.MessageHeaders) MIMEControl.Message = MailControl.MessageText MIMEControl.DecodeFromString

DecodePart Method (Mime Component)

This method decodes the specified part.

Syntax

public byte[] decodePart(int index);

Remarks

This method decodes the part specified by Index and returns the decoded part data.

DecodeFromString or DecodeFromFile must be called before calling this method. Calling this method will return the decoded bytes, and in addition, the DecodedString field will be populated with the string representation of the decoded data.

Example. Decoding a Specified Part:mime.MessageHeadersString = myMessageHeaders; mime.Message = myMessageBody; mime.DecodeFromString(); byte[] myPartContent = await mime.DecodePart(0);

DecodePartToFile Method (Mime Component)

This method decodes the specified part to a file on disk.

Syntax

public String decodePartToFile(int index);

Remarks

This method decodes the part specified by Index to a temporary file. The full path to the temporary file is returned by this method. The user is responsible for deleting the temporary file.

DecodeFromString or DecodeFromFile must be called before calling this method.

DecodePartToStream Method (Mime Component)

This method decodes the specified part to a stream.

Syntax

public void decodePartToStream(int index, java.io.OutputStream outputStream);

Remarks

This method decodes the part specified by Index to a stream specified by OutputStream.

DecodeFromString or DecodeFromFile must be called before calling this method.

EncodeToFile Method (Mime Component)

This method encodes to a file.

Syntax

public void encodeToFile();

Remarks

This method encodes the data given in Parts collection (either a decoded file or a decoded string) into a MIME message at Message and MessageHeaders using the values optionally given in Parts collection. To encode several objects into a MIME envelope, the user should first clear any old values left in the Parts collection.

The component will check for each item in Parts collection (first the decoded file and then the decoded string) for the data to encode.

The encoded message will be saved in the file pointed to by Message; the message headers will be held by MessageHeaders.

Example. Encoding Data:

MIMEControl.ResetData() MIMEControl.Parts.Add(new MIMEPart()) MIMEControl.Parts.Add(new MIMEPart()) MIMEControl.Parts[0].DecodedString = "This is plain text data" MIMEControl.Parts[0].Encoding = peQuotedPrintable MIMEControl.Parts[0].ContentType = "text/plain" MIMEControl.Parts[1].DecodedFile = "C:\filename.txt" MIMEControl.Message = "temp.tmp" MIMEControl.EncodeToFile()

EncodeToStream Method (Mime Component)

This method encodes to a stream.

Syntax

public void encodeToStream(java.io.OutputStream outputStream);

Remarks

This method encodes to a stream. It is the same as EncodeToString, but the encoded data are written to a stream instead of to the Message property.

This method encodes the data given in Parts collection into a MIME message. The Message gets written to the specified OutputStream and MessageHeaders using the values optionally given in the Parts collection. To encode several objects into a MIME envelope, the user should first clear any old values left in the Parts collection by calling ResetData.

The component will check each item in the Parts collection (first the decoded file and then the decoded string) for the data to encode.

The encoded message will be written to the specified OutputStream, and the message headers will be held by MessageHeaders.

Example. Encoding Data:

MIMEControl.ResetData() MIMEControl.Parts.Add(new MIMEPart()) MIMEControl.Parts.Add(new MIMEPart()) MIMEControl.Parts[0].DecodedString = "This is plain text data" MIMEControl.Parts[0].Encoding = peQuotedPrintable MIMEControl.Parts[0].ContentType = "text/plain" MIMEControl.Parts[1].DecodedFile = "C:\filename.txt" MIMEControl.EncodeToStream(OutputStream)

EncodeToString Method (Mime Component)

This method encodes to a string.

Syntax

public void encodeToString();

Remarks

This method encodes to a string. It is the same as EncodeToFile but the encoded data are held in the Message property rather than saved to a file.

This method encodes the data given in the Parts collection into a MIME message. The message gets stored in Message and MessageHeaders using the values optionally given in Parts collection. To encode several objects into a MIME envelope, the user should first clear any old values left in the Parts collection by calling ResetData.

The component will check each item in the Parts collection (first the decoded file and then the decoded string) for the data to encode.

The encoded message will be stored in the Message property; the message headers will be held by MessageHeaders.

Example. Encoding Data:

MIMEControl.ResetData() MIMEControl.Parts.Add(new MIMEPart()) MIMEControl.Parts.Add(new MIMEPart()) MIMEControl.Parts[0].DecodedString = "This is plain text data" MIMEControl.Parts[0].Encoding = peQuotedPrintable MIMEControl.Parts[0].ContentType = "text/plain" MIMEControl.Parts[1].DecodedFile = "C:\filename.txt" MIMEControl.EncodeToString()

Reset Method (Mime Component)

Reset the component.

Syntax

public void reset();

Remarks

This method will reset the component's properties to their default values.

ResetData Method (Mime Component)

This method resets the values of all headers and part properties.

Syntax

public void resetData();

Remarks

This method resets the values of all headers and part properties. It is an easy way to reset the component's properties before starting to populate the part properties with new values.

Error Event (Mime Component)

Fired when information is available about errors during data delivery.

Syntax

public class DefaultMimeEventListener implements MimeEventListener {
  ...
  public void error(MimeErrorEvent e) {}
  ...
}

public class MimeErrorEvent {
  public int errorCode;

  public String description;

}

Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the component throws an exception.

The ErrorCode parameter contains an error code, and the Description parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the Error Codes section.

Header Event (Mime Component)

This event is fired every time a header is parsed.

Syntax

public class DefaultMimeEventListener implements MimeEventListener {
  ...
  public void header(MimeHeaderEvent e) {}
  ...
}

public class MimeHeaderEvent {
  public int partIndex;

  public String field;

  public byte[] value;

}

Remarks

The PartIndex parameter contains the index of the part containing the current header. If the header is from the MIME body, this value will be -1. The Field parameter contains the name of the MIME header. The Value parameter contains the header contents. The Header event is fired when a header is parsed, which occurs for each header of the message when DecodeFromFile, DecodeFromString, or DecodeFromStream is called.

Progress Event (Mime Component)

This event shows the progress of decoding or encoding the input data.

Syntax

public class DefaultMimeEventListener implements MimeEventListener {
  ...
  public void progress(MimeProgressEvent e) {}
  ...
}

public class MimeProgressEvent {
  public int percentDone;

}

Remarks

The Progress allows the user to visualize the progress of processing the input data.

The PercentDone parameter shows what percentage of the input has been read.

Header Type

This is an HTTP header as it is received from the server.

Remarks

When a header is received through a Header event, it is parsed into a Header type. This type contains a Field, and its corresponding Value.

Fields

Field
String

Default Value: ""

This field contains the name of the HTTP Header (this is the same case as it is delivered).

Value
String

Default Value: ""

This field contains the Header contents.

Constructors

public Header();



public Header( field,  value);



MIMEPart Type

This is a part of the MIME message.

Remarks

Each MIME message is split into parts. A message must have at least one part to be a valid MIME message. The message itself is split into the MessageHeaders and the Message body. The body is then split into MIME parts by a specified or generated Boundary. Each part of a MIME message has its own Headers as well. These headers describe the MIMEPart and its contents.

The decoded data will be held in DecodedString or otherwise will be saved in a temporary file given by DecodedFile when the user asks for the value of the respective field.

If the encoded data are file data, the decoded file(s) will be given in the DecodedFile field. Otherwise, the decoded data will be in the DecodedString field.

When the EncodeToString method is called, the component will check for each item in the Parts collection (first the DecodedFile and then the DecodedString) for the data to encode.

Fields

ContentDisposition
String

Default Value: ""

This field contains content disposition for each part.

The value in this field is used in the Content-Disposition header. Typical values include "form-data" and "attachment". The component fills it out each time the DecodedFile is changed. Changing the ContentDisposition recalculates the Headers as well.

ContentDispositionAttr
String

Default Value: ""

This field contains the content disposition's attribute (if any) for each part.

Typical values for this field are the names of the form-variables used while creating an HTTP post or the values for filenames.

Setting this field recalculates the Headers.

ContentId
String

Default Value: ""

This field contains the content identifier for each part. The value of this field is used in the Content-Id header. The component fills it out each time the DecodedFile is changed. Changing this field recalculates the Headers as well.

ContentType
String

Default Value: ""

This field contains the content type for each part. The value of this field is used in the Content-Type header. Typical values include "image/gif" and "text/plain". The component fills it out each time the DecodedFile is changed. Changing this field recalculates the Headers as well.

ContentTypeAttr
String

Default Value: ""

This field contains the content-type attribute, if any, for each part. Setting this recalculates the Headers as well.

DecodedFile
String

Default Value: ""

This field contains the filename with the decoded data. Accessing this field for the first time after calling the DecodeFromString or DecodeFromFile method, directs the component to actually decode the part and save the data in a temporary file. The user is responsible for deleting the temporary file.

Setting a value to DecodedFile directs the component to calculate the file size and fill out the respective Size.

Note: It is recommended to use the DecodePartToFile method instead of querying this property.

DecodedString
String

Default Value: ""

This field holds the actual content of each part. The component decodes the actual part of Message to DecodedString when DecodedString's value is first queried.

Setting a value to DecodedString fills out the corresponding Size with the string size if the corresponding DecodedFile is empty.

The component checks during encoding first DecodedFile: if it is empty, then the component uses the value of DecodedString.

Note: It is recommended to use the DecodePart method instead of querying this property.

DecodedStringB
byte []

Default Value: ""

This field holds the actual content of each part. The component decodes the actual part of Message to DecodedString when DecodedString's value is first queried.

Setting a value to DecodedString fills out the corresponding Size with the string size if the corresponding DecodedFile is empty.

The component checks during encoding first DecodedFile: if it is empty, then the component uses the value of DecodedString.

Note: It is recommended to use the DecodePart method instead of querying this property.

Encoding
int

Default Value: 0

This field contains the actual content encoding type for each part. This field determines how to encode the data or how they actually were encoded in the Message, as specified in the Content-Transfer-Encoding header.

Possible values for the this field are as follows:

pe7bit (0)7 Bit data, no encoding.
peQuotedPrintable (1)Quoted-Printable encoding of (typically) text.
peBase64 (2)Base64 encoding of binary data.
pe8Bit (3)No encoding, 8-bit characters may be contained as well.
peBinary (4)Binary data without any encoding. Similar to 3 (8-bit encoding).
peUUEncode (5)Uuencoding of binary data.

Filename
String

Default Value: ""

This field contains the filename attribute specified in the headers of the part. Changing the value of the corresponding DecodedFile automatically sets the Filename and consequently the Headers.

Headers
String

Default Value: ""

This field contains the headers for each MIME part. The component fills out this field each time any of the other corresponding part properties are changed. If additional headers are needed, they should be appended after all of the other corresponding part properties are set.

Name
String

Default Value: ""

This field contains the name given to a part, such as the filename. Changing the value of DecodedFile automatically sets the corresponding Name and consequently the Headers.

PartInputStream
java.io.InputStream

Default Value: ""

This field contains a stream that contains the actual content of each part before the message is encoded.

PartOutputStream
java.io.OutputStream

Default Value: ""

The component decodes the actual part of Message when this field's value is first set and then writes the decoded value to the stream.

Note: It is recommended to use the DecodePartToStream method instead of setting this property.

Size
int (read-only)

Default Value: 0

This field contains the size of the DecodedFile or DecodedString. If a non-empty value is assigned to DecodedFile, then component fills out the corresponding Size with the file size; if the file does not exist, an error occurs.

If the DecodedFile is empty and a value is assigned to DecodedString, then the corresponding Size will be equal to the string's size.

During decoding, this field is filled with the size of that part.

Constructors

public MIMEPart();



public MIMEPart( decodedFile);



public MIMEPart( decodedString);



public MIMEPart( partInputStream);



public MIMEPart( partInputStream,  encoding);



Config Settings (Mime Component)

The component 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 component, access to these internal properties is provided through the Config method.

MIME Config Settings

AlternateCharsetNames:   Maps alternate charset names to the specified name.

Use this configuration setting to map alternate charset names to a valid charset name. The mappings are set in the following format: "AlternateCharsetNames=altName1:validName1;altName2:validname2".

The alternate names are case-insensitive to allow for a greater number of alternate names to be handled. The valid name is case-sensitive to ensure that the correct charset is used. Mappings are done on a one-to-one basis. If there are several alternate names that are not covered by case-insensitivity, multiple mappings will need to be used. Example 1. mime.Config("AlternateCharsetNames=cp-850:cp850;_cp_850:cp850"); Example 2 will map both "cp-850" and "_cp_850" to "cp850".

Example 2 is redundant, as alternate names are case-insensitive. Example 2. mime.Config("AlternateCharsetNames=cp1252:windows-1252;CP1252:windows-1252");

FoldHeaders:   Tells the component whether to fold the headers.

If True, the component 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 component whether to include the headers when encoding the message.

If True, the component 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 configuration setting 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 component should require the version header.

If True, the component 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 configuration setting is False by default.

SanitizeFilename:   Whether invalid characters are replaced in MIME part filenames.

If True, the component 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 and 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 Config Settings

BuildInfo:   Information about the product's build.

When queried, this setting will return a string containing information about the product's build.

GUIAvailable:   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 component 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 component does not attempt to process external events.

LicenseInfo:   Information about the current license.

When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information:

  • Product: The product the license is for.
  • Product Key: The key the license was generated from.
  • License Source: Where the license was found (e.g., RuntimeLicense, License File).
  • License Type: The type of license installed (e.g., Royalty Free, Single Server).
  • Last Valid Build: The last valid build number for which the license will work.
MaskSensitive:   Whether sensitive data is masked in log messages.

In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to true to mask sensitive data. The default is true.

This setting only works on these components: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.

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

If set to True (default), when the component creates a thread, the thread's Daemon property will be explicitly set to True. When set to False, the component will not set the Daemon property on the created thread. The default value is True.

UseInternalSecurityAPI:   Whether or not to use the system security libraries or an internal implementation.

When set to false, the component will use the system security libraries by default to perform cryptographic functions where applicable.

Setting this configuration setting to true tells the component to use the internal implementation instead of using the system security libraries.

This setting is set to false by default on all platforms.

Trappable Errors (Mime Component)

MIME Errors

3   Can't create the file for write (illegal name or disk is write-protected).
4   Can't open the file for read (doesn't exist?).
5   Can't read from file.
6   Can't write to file (disk full?).
280   Invalid Part Index.
281   Unknown MIME type.
282   No MIME-boundary found.
283   No file given.
284   The component is busy.
285   Can't create a temporary file to decode the data.
286   Can't read Message file.
287   No header separator found.
289   No separator found.
290   Input stream must have seeking enabled.