PHTMLMailer Component
Properties Methods Events Config Settings Errors
The PHTMLMailer component is used to send encrypted and/or signed HTML-formatted emails with or without any attachments using OpenPGP.
Syntax
TipgPHTMLMailer
Remarks
The PHTMLMailer component offers an easy-to-use interface that supports decrypting and verifying signatures of encrypted and signed emails using OpenPGP. It enables you to create messages bound for multiple recipients with different keys, simultaneously encrypt and compress with the most popular compression algorithms, and control other aspects such as the encrypting algorithm to use.
Construct the Message
To begin specify common email properties such as SendTo, Cc, BCc, Subject, and MessageText. Connection information is specified by setting MailServer and MailPort.
Encrypt
To encrypt a message specify a recipient key using the RecipientKey* properties. For instance:
PHTMLMailer1.RecipientKeyCount = 1
PHTMLMailer1.RecipientKeyKeyring(0) = "c:\my_keyring_dir"
PHTMLMailer1.RecipientKeyUserId(0) = "recipient@nsoftware.com"
The specified public key will be used to encrypt the message when Encrypt is called.
Sign
To sign a message specify a recipient key using the Key* properties. For instance:
PHTMLMailer1.KeyCount = 1
PHTMLMailer1.KeyKeyring(0) = "c:\my_keyring_dir"
PHTMLMailer1.KeyUserId(0) = "sender@nsoftware.com"
PHTMLMailer1.KeyPassphrase(0) = "password"
The specified private key will be used to sign the message when Sign is called.
Sign and Encrypt
To both sign and encrypt a message call SignAndEncrypt. The message will be signed with the private keys specified in the Key* properties and encrypted with the public keys defined in the RecipientKeys* properties.
Add Attachments
To add attachments simply call AddAttachment. The ProcessAttachments setting specifies whether attachments are also encrypted and signed.
Send
Once all the appropriate properties have been set call the Send method and the message will be sent to its intended recipient(s).
Property List
The following is the full list of the properties of the component with short descriptions. Click on the links for further details.
AttachmentCount | The number of records in the Attachment arrays. |
AttachmentFile | This property contains the path of a file on your system to be sent as an attachment with your message. |
AttachmentName | This property contains the name of the attachment to be sent. |
AuthMechanism | This property is used when connecting to the mail server. |
BCc | This property includes a comma-separated list of addresses for blind carbon copies (optional). |
Cc | This property includes a comma-separated list of addresses for carbon copies (optional). |
Command | This property is used to send additional commands directly to the server. |
CompressionMethod | The compression algorithm used. |
Connected | This shows whether the component is connected. |
DeliveryNotificationTo | This property includes the email address to which to send a delivery notification. |
EncryptingAlgorithm | The encryption algorithm used when encrypting. |
FirewallAutoDetect | This property tells the component whether or not to automatically detect and use firewall system settings, if available. |
FirewallType | This property determines the type of firewall to connect through. |
FirewallHost | This property contains the name or IP address of firewall (optional). |
FirewallPassword | This property contains a password if authentication is to be used when connecting through the firewall. |
FirewallPort | This property contains the transmission control protocol (TCP) port for the firewall Host . |
FirewallUser | This property contains a user name if authentication is to be used connecting through a firewall. |
From | The email address of the sender (required). |
HTMLFile | This property includes the path to a local HTML file. |
Idle | The current status of the component. |
ImageCount | The number of records in the Image arrays. |
ImageData | This property optionally specifies the image data. |
ImageFile | This property contains the name of the image files embedded into the HTML message. |
ImageId | This property contains the content identifier for embedded images. |
ImageType | This property contains the content type for embedded images. |
Importance | Importance of the mail message (optional). |
KeyCount | The number of records in the Key arrays. |
KeyEncoded | The key. |
KeyKeyring | The location of the keyring. |
KeyPassphrase | The passphrase for the key's secret key (if any). |
KeyUserId | The user Id of the key. |
LastReply | The last reply from the server. |
LocalHost | The name of the local host or user-assigned IP interface through which connections are initiated or accepted. |
MailPort | The server port for SMTP (default 25). |
MailServer | The name or address of a mail server (mail relay). |
MessageDate | Date of the mail message (optional). |
MessageHTML | This property includes the HTML version of the message. |
MessageId | The Message Identifier for the message. |
MessageRecipientCount | The number of records in the MessageRecipient arrays. |
MessageRecipientAddress | This property contains the email address of the recipient. |
MessageRecipientName | This property contains the name of the recipient. |
MessageRecipientOptions | This property contains the recipient sending options (used only by SMTP). |
MessageRecipientType | This property contains the recipient type: To, Cc, or Bcc. |
MessageText | This property includes the plaintext version of the message. |
OtherHeaders | An RFC 822 compliant string consisting of extra headers. |
ParseHTML | This property controls the behavior of the MessageHTML property. |
Password | A password for logon to the MailServer . |
Priority | Priority of the mail message (optional). |
ReadReceiptTo | Email address to send a read receipt to. |
RecipientKeyCount | The number of records in the RecipientKey arrays. |
RecipientKeyEncoded | The key. |
RecipientKeyKeyring | The location of the keyring. |
RecipientKeyUserId | The user Id of the key. |
ReplyTo | A mail address to which to reply (optional). |
SendTo | A comma separated list of addresses for destinations (required). |
Sensitivity | Sensitivity of the mail message (optional). |
SigningAlgorithm | The signature hash algorithm used when signing. |
SSLAcceptServerCertEncoded | This is the certificate (PEM/base64 encoded). |
SSLCertEncoded | This is the certificate (PEM/base64 encoded). |
SSLCertStore | This is the name of the certificate store for the client certificate. |
SSLCertStorePassword | If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store. |
SSLCertStoreType | This is the type of certificate store for this certificate. |
SSLCertSubject | This is the subject of the certificate used for client authentication. |
SSLEnabled | Whether TLS/SSL is enabled. |
SSLProvider | This specifies the SSL/TLS implementation to use. |
SSLServerCertEncoded | This is the certificate (PEM/base64 encoded). |
SSLStartMode | Determines how the component starts the SSL negotiation. |
Subject | The subject of the mail message (optional). |
Timeout | A timeout for the component. |
User | A user identifier to login as in the MailServer . |
Method List
The following is the full list of the methods of the component with short descriptions. Click on the links for further details.
AddAttachment | This adds FileName as an attachment. |
Config | Sets or retrieves a configuration setting. |
Connect | This method connects to the mail relay and sends the SMTP HELO command. |
Disconnect | This method disconnects from the SMTP server. |
DoEvents | Processes events from the internal message queue. |
Encrypt | Encrypts the message. |
Interrupt | Interrupt the current method. |
ProcessQueue | Sends the messages which have previously been queued into QueueDir . |
Queue | Queues the message into QueueDir . |
ResetHeaders | Resets all the message headers to empty. |
Send | This method sends the current message and MIME-encoded attachment. |
Sign | Signs the message. |
SignAndEncrypt | Signs and encrypts the current message. |
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.
ConnectionStatus | This event is fired to indicate changes in the connection state. |
EndTransfer | This event is fired when the message text completes transferring. |
Error | Information about errors during data delivery. |
KeyPassphrase | Fired if the passphrase of current key is incorrect or empty. |
PITrail | Traces the commands sent to the mail server, and the respective replies. |
Progress | Fired as progress is made. |
SSLServerAuthentication | Fired after the server presents its certificate to the client. |
SSLStatus | Shows the progress of the secure connection. |
StartTransfer | Fired when the message text starts transferring. |
Status | Shows the progress of the operation. |
Transfer | Fired while the message text gets transferred to MailServer . |
Config Settings
The following is a list of config settings for the component with short descriptions. Click on the links for further details.
ClearSignature | Specifies whether or not to create a cleartext signature. |
Comment | The OpenPGP message comment. |
CompressionLevel | The level of compression used. |
EnsureValidDSASignatureHashAlgorithm | Whether or not to select a suitable signature hash algorithm automatically. |
LogLevel | Specifies the level of detail that is logged. |
ProcessAttachments | Whether or not to process attachments. |
SymmetricPassphrase | The password used for symmetric encryption or decryption. |
VersionHeader | The Version header value in the ASCII armored OpenPGP message. |
AttachmentEncoding[index] | Content-Transfer-Encoding for attached file (at index). |
AttachmentText[index] | Add the text into the attachment at the specified index. |
AttachmentType[index] | Content-type for attached file (at index). |
Charset | When set, the charset Content-Type attribute will be added using the specified value. |
ExcludeTags | Specifies tags that will be excluded when calculating MessageText. |
MessageTextEncoding | When set, the MessageHTML and MessageText values will be encoded using the specified encoding. |
OverrideFilename | If set to true, the AttachmentName property value will be used to set the MIME part Filename attribute. |
TempFilePath | If set, the temporary files created during message creation will be put in the path specified. |
UseTempFile | If set, the component uses temporary files when generating messages. |
AllowEmptyTo | If set to True, then the SendTo property is not required. |
AuthorizationIdentity | The value to use as the authorization identity when SASL authentication is used. |
Charset | When set, the message headers will be encoded using the specified Charset. |
Hello | The argument for HELO (herald) command to the server (defaults to local host name). |
KeepQueue | If set to True, queued files are not deleted after a successful send. |
MaxHeaderLength | Maximum length for headers to avoid line folding (default 80). |
MessageHeadersString | String representation of RFC822-encoded headers of the message. |
MessageIdAlgorithm | Determines the algorithm used to hash the random MessageId. |
OtherHeaders | An RFC 822 compliant string consisting of extra headers. |
ReturnPath | Sets the Return-Path to be used for sending email. |
SendRSET | Whether to send RSET command. |
StopOnBccErrors | Instructs the component to stop sending the message if the server does not acknowledge any of the BCCs. |
StopOnCcErrors | Instructs the component to stop sending the message if the server does not acknowledge any of the CCs. |
StopOnToErrors | Instructs the component to stop sending the message if the server does not acknowledge any of the TOs. |
TransferText | String representation of RFC822-encoded body of the message. |
ConnectionTimeout | Sets a separate timeout value for establishing a connection. |
FirewallAutoDetect | Tells the component whether or not to automatically detect and use firewall system settings, if available. |
FirewallHost | Name or IP address of firewall (optional). |
FirewallPassword | Password to be used if authentication is to be used when connecting through the firewall. |
FirewallPort | The TCP port for the FirewallHost;. |
FirewallType | Determines the type of firewall to connect through. |
FirewallUser | A user name if authentication is to be used connecting through a firewall. |
KeepAliveInterval | The retry interval, in milliseconds, to be used when a TCP keep-alive packet is sent and no response is received. |
KeepAliveTime | The inactivity time in milliseconds before a TCP keep-alive packet is sent. |
Linger | When set to True, connections are terminated gracefully. |
LingerTime | Time in seconds to have the connection linger. |
LocalHost | The name of the local host through which connections are initiated or accepted. |
LocalPort | The port in the local host where the component binds. |
MaxLineLength | The maximum amount of data to accumulate when no EOL is found. |
MaxTransferRate | The transfer rate limit in bytes per second. |
ProxyExceptionsList | A semicolon separated list of hosts and IPs to bypass when using a proxy. |
TCPKeepAlive | Determines whether or not the keep alive socket option is enabled. |
TcpNoDelay | Whether or not to delay when sending packets. |
UseIPv6 | Whether to use IPv6. |
LogSSLPackets | Controls whether SSL packets are logged when using the internal security API. |
OpenSSLCADir | The path to a directory containing CA certificates. |
OpenSSLCAFile | Name of the file containing the list of CA's trusted by your application. |
OpenSSLCipherList | A string that controls the ciphers to be used by SSL. |
OpenSSLPrngSeedData | The data to seed the pseudo random number generator (PRNG). |
ReuseSSLSession | Determines if the SSL session is reused. |
SSLCACerts | A newline separated list of CA certificate to use during SSL client authentication. |
SSLCheckCRL | Whether to check the Certificate Revocation List for the server certificate. |
SSLCheckOCSP | Whether to use OCSP to check the status of the server certificate. |
SSLCipherStrength | The minimum cipher strength used for bulk encryption. |
SSLEnabledCipherSuites | The cipher suite to be used in an SSL negotiation. |
SSLEnabledProtocols | Used to enable/disable the supported security protocols. |
SSLEnableRenegotiation | Whether the renegotiation_info SSL extension is supported. |
SSLIncludeCertChain | Whether the entire certificate chain is included in the SSLServerAuthentication event. |
SSLKeyLogFile | The location of a file where per-session secrets are written for debugging purposes. |
SSLNegotiatedCipher | Returns the negotiated cipher suite. |
SSLNegotiatedCipherStrength | Returns the negotiated cipher suite strength. |
SSLNegotiatedCipherSuite | Returns the negotiated cipher suite. |
SSLNegotiatedKeyExchange | Returns the negotiated key exchange algorithm. |
SSLNegotiatedKeyExchangeStrength | Returns the negotiated key exchange algorithm strength. |
SSLNegotiatedVersion | Returns the negotiated protocol version. |
SSLSecurityFlags | Flags that control certificate verification. |
SSLServerCACerts | A newline separated list of CA certificate to use during SSL server certificate validation. |
TLS12SignatureAlgorithms | Defines the allowed TLS 1.2 signature algorithms when SSLProvider is set to Internal. |
TLS12SupportedGroups | The supported groups for ECC. |
TLS13KeyShareGroups | The groups for which to pregenerate key shares. |
TLS13SignatureAlgorithms | The allowed certificate signature algorithms. |
TLS13SupportedGroups | The supported groups for (EC)DHE key exchange. |
AbsoluteTimeout | Determines whether timeouts are inactivity timeouts or absolute timeouts. |
FirewallData | Used to send extra data to the firewall. |
InBufferSize | The size in bytes of the incoming queue of the socket. |
OutBufferSize | The size in bytes of the outgoing queue of the socket. |
BuildInfo | Information about the product's build. |
CodePage | The system code page used for Unicode to Multibyte translations. |
LicenseInfo | Information about the current license. |
MaskSensitive | Whether sensitive data is masked in log messages. |
UseInternalSecurityAPI | Tells the component whether or not to use the system security libraries or an internal implementation. |
AttachmentCount Property (PHTMLMailer Component)
The number of records in the Attachment arrays.
Syntax
__property int AttachmentCount = { read=FAttachmentCount, write=FSetAttachmentCount };
Default Value
0
Remarks
This property controls the size of the following arrays:
The array indices start at 0 and end at AttachmentCount - 1.This property is not available at design time.
Data Type
Integer
AttachmentFile Property (PHTMLMailer Component)
This property contains the path of a file on your system to be sent as an attachment with your message.
Syntax
__property String AttachmentFile[int AttachmentIndex] = { read=FAttachmentFile, write=FSetAttachmentFile };
Default Value
""
Remarks
This property contains the path of a file on your system to be sent as an attachment with your message.
The AttachmentIndex parameter specifies the index of the item in the array. The size of the array is controlled by the AttachmentCount property.
This property is not available at design time.
Data Type
String
AttachmentName Property (PHTMLMailer Component)
This property contains the name of the attachment to be sent.
Syntax
__property String AttachmentName[int AttachmentIndex] = { read=FAttachmentName, write=FSetAttachmentName };
Default Value
""
Remarks
This property contains the name of the attachment to be sent.
The AttachmentIndex parameter specifies the index of the item in the array. The size of the array is controlled by the AttachmentCount property.
This property is not available at design time.
Data Type
String
AuthMechanism Property (PHTMLMailer Component)
This property is used when connecting to the mail server.
Syntax
__property TipgPHTMLMailerAuthMechanisms AuthMechanism = { read=FAuthMechanism, write=FSetAuthMechanism };
enum TipgPHTMLMailerAuthMechanisms { amUserPassword=0, amCRAMMD5=1, amNTLM=2, amAPOP=3, amSASLPlain=4, amSASLDigestMD5=5, amKerberos=6, amXOAUTH2=7 };
Default Value
amUserPassword
Remarks
This is the authentication mechanism property to be used when connecting to the mail server.
By default, this property is amUserPassword (0), and if the User and Password properties are set, the AUTH command is sent to the server for authentication. If this property is set to amCRAMMD5 (1), CRAM-MD5 authentication is used instead.
If this property is set to amNTLM (2), NTLM authentication will be used.
If this property is set to amKerberos (6), Kerberos authentication will be used.
Note: This functionality is available only in Windows.
When set to amXOAUTH2 (7), set User to the username and AuthorizationIdentity to the OAuth token. See AuthorizationIdentity for details.
Data Type
Integer
BCc Property (PHTMLMailer Component)
This property includes a comma-separated list of addresses for blind carbon copies (optional).
Syntax
__property String BCc = { read=FBCc, write=FSetBCc };
Default Value
""
Remarks
This property specifies a comma-separated list of destinations for blind carbon copies of the mail message. A copy of the message is sent to each destination. Because no BCc SMTP header is created containing the destination addresses, individual recipients never see the list of the other recipients.
The component will return an error if the MailServer returns an error code about any email address specified in SendTo or Cc but it will fire an Error event only if the same thing happens with an email address specified in this property.
If the resulting header is longer than MaxHeaderLength, then it is folded according to RFC 822 specifications.
Note: You must clear the MessageRecipients properties before setting this property to remove previous recipients.
Data Type
String
Cc Property (PHTMLMailer Component)
This property includes a comma-separated list of addresses for carbon copies (optional).
Syntax
__property String Cc = { read=FCc, write=FSetCc };
Default Value
""
Remarks
This property specifies a comma-separated list of destinations for carbon copies of the mail message. A copy of the message is sent to each destination, and a Cc SMTP header is created containing the destination addresses. This header is sent to every recipient of the message. If you don't want to copy this information to every recipient, then use blind carbon copies instead (see the description of the BCc).
The component will return an error if the MailServer returns an error code about any email address specified in SendTo or Cc but it will fire an Error event only if the same thing happens with an email address specified in BCc.
If the resulting header is longer than MaxHeaderLength, then it is folded according to RFC 822 specifications.
Note: You must clear the MessageRecipients properties before setting this property to remove previous recipients.
Data Type
String
Command Property (PHTMLMailer Component)
This property is used to send additional commands directly to the server.
Syntax
__property String Command = { write=FSetCommand };
Default Value
""
Remarks
This property can be used to send additional commands directly to the server. Check the LastReply property or trap the PITrail events coming from the server to get the response.
This property is write-only and not available at design time.
Data Type
String
CompressionMethod Property (PHTMLMailer Component)
The compression algorithm used.
Syntax
__property String CompressionMethod = { read=FCompressionMethod, write=FSetCompressionMethod };
Default Value
"zip"
Remarks
This property specifies which compression method is used when generating output. Possible values are:
- zip (default)
- zlib
- bzip2
- none or uncompressed
Data Type
String
Connected Property (PHTMLMailer Component)
This shows whether the component is connected.
Syntax
__property bool Connected = { read=FConnected, write=FSetConnected };
Default Value
False
Remarks
This property is used to determine whether or not the component is connected to the remote host.
Note: It is recommended to use the Connect or Disconnect method instead of setting this property.
This property is not available at design time.
Data Type
Boolean
DeliveryNotificationTo Property (PHTMLMailer Component)
This property includes the email address to which to send a delivery notification.
Syntax
__property String DeliveryNotificationTo = { read=FDeliveryNotificationTo, write=FSetDeliveryNotificationTo };
Default Value
""
Remarks
This property contains the email address to send to which to send a delivery notification. When set, a Return-Receipt-To header is added to the message. This property should be set to an email address that can receive the delivery notification.
Data Type
String
EncryptingAlgorithm Property (PHTMLMailer Component)
The encryption algorithm used when encrypting.
Syntax
__property String EncryptingAlgorithm = { read=FEncryptingAlgorithm, write=FSetEncryptingAlgorithm };
Default Value
"AES128"
Remarks
This property specifies the encryption algorithm used when encrypting. Possible values are:
- CAST5
- 3DES or TripleDES
- AES256
- AES192
- AES128 (default)
- BLOWFISH
- TWOFISH
- IDEA
Data Type
String
FirewallAutoDetect Property (PHTMLMailer Component)
This property tells the component whether or not to automatically detect and use firewall system settings, if available.
Syntax
__property bool FirewallAutoDetect = { read=FFirewallAutoDetect, write=FSetFirewallAutoDetect };
Default Value
False
Remarks
This property tells the component whether or not to automatically detect and use firewall system settings, if available.
Data Type
Boolean
FirewallType Property (PHTMLMailer Component)
This property determines the type of firewall to connect through.
Syntax
__property TipgPHTMLMailerFirewallTypes FirewallType = { read=FFirewallType, write=FSetFirewallType };
enum TipgPHTMLMailerFirewallTypes { fwNone=0, fwTunnel=1, fwSOCKS4=2, fwSOCKS5=3, fwSOCKS4A=10 };
Default Value
fwNone
Remarks
This property determines the type of firewall to connect through. The applicable values are as follows:
fwNone (0) | No firewall (default setting). |
fwTunnel (1) | Connect through a tunneling proxy. FirewallPort is set to 80. |
fwSOCKS4 (2) | Connect through a SOCKS4 Proxy. FirewallPort is set to 1080. |
fwSOCKS5 (3) | Connect through a SOCKS5 Proxy. FirewallPort is set to 1080. |
fwSOCKS4A (10) | Connect through a SOCKS4A Proxy. FirewallPort is set to 1080. |
Data Type
Integer
FirewallHost Property (PHTMLMailer Component)
This property contains the name or IP address of firewall (optional).
Syntax
__property String FirewallHost = { read=FFirewallHost, write=FSetFirewallHost };
Default Value
""
Remarks
This property contains the name or IP address of firewall (optional). If a FirewallHost is given, the requested connections will be authenticated through the specified firewall when connecting.
If this property is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, this property is set to the corresponding address. If the search is not successful, the component raises an exception.
Data Type
String
FirewallPassword Property (PHTMLMailer Component)
This property contains a password if authentication is to be used when connecting through the firewall.
Syntax
__property String FirewallPassword = { read=FFirewallPassword, write=FSetFirewallPassword };
Default Value
""
Remarks
This property contains a password if authentication is to be used when connecting through the firewall. If FirewallHost is specified, the FirewallUser and FirewallPassword properties are used to connect and authenticate to the given firewall. If the authentication fails, the component raises an exception.
Data Type
String
FirewallPort Property (PHTMLMailer Component)
This property contains the transmission control protocol (TCP) port for the firewall Host .
Syntax
__property int FirewallPort = { read=FFirewallPort, write=FSetFirewallPort };
Default Value
0
Remarks
This property contains the transmission control protocol (TCP) port for the firewall FirewallHost. See the description of the FirewallHost property for details.
Note: This property is set automatically when FirewallType is set to a valid value. See the description of the FirewallType property for details.
Data Type
Integer
FirewallUser Property (PHTMLMailer Component)
This property contains a user name if authentication is to be used connecting through a firewall.
Syntax
__property String FirewallUser = { read=FFirewallUser, write=FSetFirewallUser };
Default Value
""
Remarks
This property contains a user name if authentication is to be used connecting through a firewall. If the FirewallHost is specified, this property and FirewallPassword properties are used to connect and authenticate to the given Firewall. If the authentication fails, the component raises an exception.
Data Type
String
From Property (PHTMLMailer Component)
The email address of the sender (required).
Syntax
__property String From = { read=FFrom, write=FSetFrom };
Default Value
""
Remarks
This property is used to create a From SMTP header. This header identifies the sender of the message. A valid email address is required. Examples of valid addresses are: "Friendly Name" <address@company.com> or address@company.com
If the resulting header is longer than MaxHeaderLength, then it is folded according to RFC 822 specifications.
Data Type
String
HTMLFile Property (PHTMLMailer Component)
This property includes the path to a local HTML file.
Syntax
__property String HTMLFile = { read=FHTMLFile, write=FSetHTMLFile };
Default Value
""
Remarks
This property may contain the path to the local HTML file. If this property is not empty, the contents of the file with that name will be appended to the text in MessageHTML.
Note: This means that if MessageHTML is empty, HTMLFile is what will be sent to the server.
This property is not available at design time.
Data Type
String
Idle Property (PHTMLMailer Component)
The current status of the component.
Syntax
__property bool Idle = { read=FIdle };
Default Value
True
Remarks
Idle will be False if the component is currently busy (communicating and/or waiting for an answer), and True at all other times.
This property is read-only.
Data Type
Boolean
ImageCount Property (PHTMLMailer Component)
The number of records in the Image arrays.
Syntax
__property int ImageCount = { read=FImageCount, write=FSetImageCount };
Default Value
0
Remarks
This property controls the size of the following arrays:
The array indices start at 0 and end at ImageCount - 1.This property is not available at design time.
Data Type
Integer
ImageData Property (PHTMLMailer Component)
This property optionally specifies the image data.
Syntax
__property String ImageData[int ImageIndex] = { read=FImageData, write=FSetImageData }; __property DynamicArray<Byte> ImageDataB[int ImageIndex] = { read=FImageDataB, write=FSetImageDataB };
Default Value
""
Remarks
This property optionally specifies the image data. This may be used instead of specifying an image by file. The value specified here may be either the hex-encoded image data or the raw unencoded image data.
The ImageIndex parameter specifies the index of the item in the array. The size of the array is controlled by the ImageCount property.
This property is not available at design time.
Data Type
Byte Array
ImageFile Property (PHTMLMailer Component)
This property contains the name of the image files embedded into the HTML message.
Syntax
__property String ImageFile[int ImageIndex] = { read=FImageFile, write=FSetImageFile };
Default Value
""
Remarks
This property contains the name of the image files embedded into the HTML message. This value is updated every time MessageHTML is set. You may change the file names before sending (e.g., if they don't point to valid files).
The ImageIndex parameter specifies the index of the item in the array. The size of the array is controlled by the ImageCount property.
This property is not available at design time.
Data Type
String
ImageId Property (PHTMLMailer Component)
This property contains the content identifier for embedded images.
Syntax
__property String ImageId[int ImageIndex] = { read=FImageId, write=FSetImageId };
Default Value
""
Remarks
This property contains the content identifier for embedded images. This value is computed automatically, unless ParseHTML is False, in which case you are responsible for providing it.
The ImageIndex parameter specifies the index of the item in the array. The size of the array is controlled by the ImageCount property.
This property is not available at design time.
Data Type
String
ImageType Property (PHTMLMailer Component)
This property contains the content type for embedded images.
Syntax
__property String ImageType[int ImageIndex] = { read=FImageType, write=FSetImageType };
Default Value
""
Remarks
This property contains the content type for embedded images. This value is determined automatically, unless ParseHTML is False, in which case you are responsible for providing it.
The ImageIndex parameter specifies the index of the item in the array. The size of the array is controlled by the ImageCount property.
This property is not available at design time.
Data Type
String
Importance Property (PHTMLMailer Component)
Importance of the mail message (optional).
Syntax
__property TipgPHTMLMailerImportances Importance = { read=FImportance, write=FSetImportance };
enum TipgPHTMLMailerImportances { miUnspecified=0, miHigh=1, miNormal=2, miLow=3 };
Default Value
miUnspecified
Remarks
This property indicates the importance of the mail message (optional). When set, an Importance header will be added to the message.
Importance is an indication to the recipient(s) about how important the message is. The possible values are Unspecified (0), High (1), Normal (2), and Low (3).
Data Type
Integer
KeyCount Property (PHTMLMailer Component)
The number of records in the Key arrays.
Syntax
__property int KeyCount = { read=FKeyCount, write=FSetKeyCount };
Default Value
0
Remarks
This property controls the size of the following arrays:
The array indices start at 0 and end at KeyCount - 1.This property is not available at design time.
Data Type
Integer
KeyEncoded Property (PHTMLMailer Component)
The key.
Syntax
__property String KeyEncoded[int KeyIndex] = { read=FKeyEncoded, write=FSetKeyEncoded }; __property DynamicArray<Byte> KeyEncodedB[int KeyIndex] = { read=FKeyEncodedB, write=FSetKeyEncodedB };
Default Value
""
Remarks
The key. This property is used to assign a specific key. The KeyUserId properties may also be used to specify a key.
The KeyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the KeyCount property.
This property is not available at design time.
Data Type
Byte Array
KeyKeyring Property (PHTMLMailer Component)
The location of the keyring.
Syntax
__property String KeyKeyring[int KeyIndex] = { read=FKeyKeyring, write=FSetKeyKeyring };
Default Value
""
Remarks
The location of the keyring.
If the keyring is stored in a directory, set this property to the directory. The directory must contain the files "secring.gpg" and "pubring.gpg". A keyring may also be stored in a single file. If the keyring is a file this property should be set to the path of the file.
When This property is set the component will read the keyring and populate the Key* properties with the first key found in the keyring. Set KeyUserId to select a different key in the current keyring.
The KeyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the KeyCount property.
This property is not available at design time.
Data Type
String
KeyPassphrase Property (PHTMLMailer Component)
The passphrase for the key's secret key (if any).
Syntax
__property String KeyPassphrase[int KeyIndex] = { read=FKeyPassphrase, write=FSetKeyPassphrase };
Default Value
""
Remarks
The passphrase for the key's secret key (if any). This must be specified before operations requiring the secret key are attempted. The passphrase may be supplied in this property or through the KeyPassphrase event, which will fire when a passphrase is required.
The passphrase is required when using the following methods in KeyMgr:
- AddUserId
- SignUserId
- ChangeExpirationDate
- ChangePassphrase
When using the OpenPGP component, or an email-based component, the following methods require a passphrase for the key:
- Decrypt
- Sign
- SignAndEncrypt
The KeyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the KeyCount property.
This property is not available at design time.
Data Type
String
KeyUserId Property (PHTMLMailer Component)
The user Id of the key.
Syntax
__property String KeyUserId[int KeyIndex] = { read=FKeyUserId, write=FSetKeyUserId };
Default Value
""
Remarks
The user Id of the key. When a key is loaded this property is populated with the user Id associated with the key. This property may be set to load a key from the Keyring. When this property is set the component will search the Keyring for a key associated with the UserId specified.
When loading a key with multiple user Ids, this property will be populated with the UserId that was most recently added to the key. To discover all of the UserIds associated with a key query this property and KeyOtherUserIds after loading the key.
The UserId format is:
FirstName LastName (Comment) <Email>Not all values are required when selecting or generating a key, but at least FirstName or Email are required.
When using this property to select a key you may also specify the key's Id, or any of its subkeys' Ids, instead of a user Id. The component will then search for a key with a matching Id. This is helpful in situations where you do not have the UserId but still need to load the key, such as within the OpenPGP component's RecipientInfo event.
The KeyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the KeyCount property.
This property is not available at design time.
Data Type
String
LastReply Property (PHTMLMailer Component)
The last reply from the server.
Syntax
__property String LastReply = { read=FLastReply };
Default Value
""
Remarks
This property indicates the last reply received from the server. It can be used for informational purposes. The same information and more can also be retrieved through the PITrail event.
This property is read-only.
Data Type
String
LocalHost Property (PHTMLMailer Component)
The name of the local host or user-assigned IP interface through which connections are initiated or accepted.
Syntax
__property String LocalHost = { read=FLocalHost, write=FSetLocalHost };
Default Value
""
Remarks
The LocalHost property contains the name of the local host as obtained by the gethostname() system call, or if the user has assigned an IP address, the value of that address.
In multi-homed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the component initiate connections (or accept in the case of server components) only through that interface.
If the component is connected, the LocalHost property shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multi-homed hosts (machines with more than one IP interface).
NOTE: LocalHost is not persistent. You must always set it in code, and never in the property window.
Data Type
String
MailPort Property (PHTMLMailer Component)
The server port for SMTP (default 25).
Syntax
__property int MailPort = { read=FMailPort, write=FSetMailPort };
Default Value
25
Remarks
This property contains the server port for SMTP (default 25). A valid port number (a value between 1 and 65535) is required for the connection to take place. The property must be set before a connection is attempted and cannot be changed once a connection is established. Any attempt to change this property while connected will fail with an error.
For implicit SSL, use port 465 (please refer to the SSLStartMode property for more information).
This property is not available at design time.
Data Type
Integer
MailServer Property (PHTMLMailer Component)
The name or address of a mail server (mail relay).
Syntax
__property String MailServer = { read=FMailServer, write=FSetMailServer };
Default Value
""
Remarks
This property specifies the IP address (IP number in dotted internet format) or Domain Name for a mail relay through which messages will be routed. It is set before a connection is attempted and cannot be changed once a connection is in progress.
The current version of the component does not provide a default value for the mail relay. You must provide a host name yourself. Generally, any internet host with an SMTP server will suffice (a UNIX host for example), but it is preferable to select a MailServer that is close to the machine sending mail.
If this property is set to a Domain Name, a DNS request is initiated and upon successful termination of the request, this property is set to the corresponding address. If the search is not successful, an error is returned.
If the component is configured to use a SOCKS firewall, the value assigned to this property may be preceded with an "*". If this is the case, the host name is passed to the firewall unresolved and the firewall performs the DNS resolution.
Data Type
String
MessageDate Property (PHTMLMailer Component)
Date of the mail message (optional).
Syntax
__property String MessageDate = { read=FMessageDate, write=FSetMessageDate };
Default Value
"*"
Remarks
If this property contains a non-empty string, then a Date SMTP header is created and attached to the message. If it is an empty string, then the date information is added by the mail relay(s) the message goes through.
Special case: if this property is set to the special value "*", a Date SMTP header reflecting the current date and time is generated when MessageHeaders is computed and the message is sent. This is the default behavior of the component
RFC 822 contains detailed date format specifications. An example of a valid date is "Fri, 1 Mar 96 21:24:52 EST".
This property is not available at design time.
Data Type
String
MessageHTML Property (PHTMLMailer Component)
This property includes the HTML version of the message.
Syntax
__property String MessageHTML = { read=FMessageHTML, write=FSetMessageHTML };
Default Value
""
Remarks
This property contains the HTML version of the message.
When this property is set, the component automatically computes a plaintext version of the text and puts it into MessageText. You may choose to override this default text with your own version.
Example. Setting MessageHTML:
component.MessageHTML = "<b>Hello</b>, my name is <i>Tom</i>";
Data Type
String
MessageId Property (PHTMLMailer Component)
The Message Identifier for the message.
Syntax
__property String MessageId = { read=FMessageId, write=FSetMessageId };
Default Value
"*"
Remarks
This property contains the Message Identifier for the message. When set, the value of MessageId is used as the Message-ID header value of the message. A special value of "*" will automatically generate a random unique identifier for the message.
This property is not available at design time.
Data Type
String
MessageRecipientCount Property (PHTMLMailer Component)
The number of records in the MessageRecipient arrays.
Syntax
__property int MessageRecipientCount = { read=FMessageRecipientCount, write=FSetMessageRecipientCount };
Default Value
0
Remarks
This property controls the size of the following arrays:
The array indices start at 0 and end at MessageRecipientCount - 1.This property is not available at design time.
Data Type
Integer
MessageRecipientAddress Property (PHTMLMailer Component)
This property contains the email address of the recipient.
Syntax
__property String MessageRecipientAddress[int RecipientIndex] = { read=FMessageRecipientAddress, write=FSetMessageRecipientAddress };
Default Value
""
Remarks
This property contains the email address of the recipient.
The RecipientIndex parameter specifies the index of the item in the array. The size of the array is controlled by the MessageRecipientCount property.
This property is not available at design time.
Data Type
String
MessageRecipientName Property (PHTMLMailer Component)
This property contains the name of the recipient.
Syntax
__property String MessageRecipientName[int RecipientIndex] = { read=FMessageRecipientName, write=FSetMessageRecipientName };
Default Value
""
Remarks
This property contains the name of the recipient.
The RecipientIndex parameter specifies the index of the item in the array. The size of the array is controlled by the MessageRecipientCount property.
This property is not available at design time.
Data Type
String
MessageRecipientOptions Property (PHTMLMailer Component)
This property contains the recipient sending options (used only by SMTP).
Syntax
__property String MessageRecipientOptions[int RecipientIndex] = { read=FMessageRecipientOptions, write=FSetMessageRecipientOptions };
Default Value
""
Remarks
This property contains the recipient sending options (used only by SMTP). This must be a string of RFC-compliant recipient options (used by SMTP).
One type of option is a delivery status notification sent per recipient, which is specified by RFC 1891.
component.MessageRecipientOptions(0) = "NOTIFY SUCCESS,FAILURE,DELAY";
The RecipientIndex parameter specifies the index of the item in the array. The size of the array is controlled by the MessageRecipientCount property.
This property is not available at design time.
Data Type
String
MessageRecipientType Property (PHTMLMailer Component)
This property contains the recipient type: To, Cc, or Bcc.
Syntax
__property TipgPHTMLMailerMessageRecipientTypes MessageRecipientType[int RecipientIndex] = { read=FMessageRecipientType, write=FSetMessageRecipientType };
enum TipgPHTMLMailerMessageRecipientTypes { rtTo=0, rtCc=1, rtBCc=2 };
Default Value
rtTo
Remarks
This property contains the recipient type: To, Cc, or Bcc.
The RecipientIndex parameter specifies the index of the item in the array. The size of the array is controlled by the MessageRecipientCount property.
This property is not available at design time.
Data Type
Integer
MessageText Property (PHTMLMailer Component)
This property includes the plaintext version of the message.
Syntax
__property String MessageText = { read=FMessageText, write=FSetMessageText };
Default Value
""
Remarks
This property is a plaintext version of the HTML message. This is necessary for recipients with legacy mail readers that do not support HTML.
The MessageHTML property contains the HTML version of the message. When MessageHTML is set, the component automatically computes a plaintext version of the text and puts it into this property. You may choose to override this default text with your own version.
Data Type
String
OtherHeaders Property (PHTMLMailer Component)
An RFC 822 compliant string consisting of extra headers.
Syntax
__property String OtherHeaders = { read=FOtherHeaders, write=FSetOtherHeaders };
Default Value
""
Remarks
This property contains a string of headers to be appended to the message headers created from other properties like SendTo, Subject, etc.
The headers must be of the format "header: value" as specified in RFC 822. Header lines should be separated by CRLF ("\r\n") .
Use this property with caution. If this property contains invalid headers, message delivery might not be successful.
This property is useful for extending the functionality of the component. A good example is delivery of MIME encoded messages.
SPECIAL CASE: if this property starts with an empty line (CRLF), then the value of this property is used instead of the normally computed message headers.
Example (Send an Email With Additional Header)
component.MailServer = "MyServer";
component.From = "me@server.com";
component.SendTo = "recipient@server.com";
component.Subject = "My Subject";
component.MessageText = "This is the message body.";
component.OtherHeaders = "HeaderName: HeaderValue";
component.Send();
This property is not available at design time.
Data Type
String
ParseHTML Property (PHTMLMailer Component)
This property controls the behavior of the MessageHTML property.
Syntax
__property bool ParseHTML = { read=FParseHTML, write=FSetParseHTML };
Default Value
true
Remarks
This property controls the behavior of the MessageHTML property. If ParseHTML is set to False, you must provide valid values in MessageHTML, MessageText, and Images.
Data Type
Boolean
Password Property (PHTMLMailer Component)
A password for logon to the MailServer .
Syntax
__property String Password = { read=FPassword, write=FSetPassword };
Default Value
""
Remarks
If this property is set to a non-empty string, then when connecting to the MailServer an AUTH or CRAM-MD5 (depending on the value of AuthMechanism) command is sent in order to provide authentication information for the user.
This property is not available at design time.
Data Type
String
Priority Property (PHTMLMailer Component)
Priority of the mail message (optional).
Syntax
__property TipgPHTMLMailerPriorities Priority = { read=FPriority, write=FSetPriority };
enum TipgPHTMLMailerPriorities { epUnspecified=0, epNormal=1, epUrgent=2, epNonUrgent=3 };
Default Value
epUnspecified
Remarks
When this property is set, a Priority header will be added to the message. Priority is an indication about the delivery priority of the message. The possible values are epNormal, epUrgent, and epNonUrgent.
Data Type
Integer
ReadReceiptTo Property (PHTMLMailer Component)
Email address to send a read receipt to.
Syntax
__property String ReadReceiptTo = { read=FReadReceiptTo, write=FSetReadReceiptTo };
Default Value
""
Remarks
When this property is set, a Disposition-Notification-To header is added to the message. This property should be set to an email address which should receive the read-receipt.
Data Type
String
RecipientKeyCount Property (PHTMLMailer Component)
The number of records in the RecipientKey arrays.
Syntax
__property int RecipientKeyCount = { read=FRecipientKeyCount, write=FSetRecipientKeyCount };
Default Value
0
Remarks
This property controls the size of the following arrays:
The array indices start at 0 and end at RecipientKeyCount - 1.This property is not available at design time.
Data Type
Integer
RecipientKeyEncoded Property (PHTMLMailer Component)
The key.
Syntax
__property String RecipientKeyEncoded[int RecipientKeyIndex] = { read=FRecipientKeyEncoded, write=FSetRecipientKeyEncoded }; __property DynamicArray<Byte> RecipientKeyEncodedB[int RecipientKeyIndex] = { read=FRecipientKeyEncodedB, write=FSetRecipientKeyEncodedB };
Default Value
""
Remarks
The key. This property is used to assign a specific key. The RecipientKeyUserId properties may also be used to specify a key.
The RecipientKeyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the RecipientKeyCount property.
This property is not available at design time.
Data Type
Byte Array
RecipientKeyKeyring Property (PHTMLMailer Component)
The location of the keyring.
Syntax
__property String RecipientKeyKeyring[int RecipientKeyIndex] = { read=FRecipientKeyKeyring, write=FSetRecipientKeyKeyring };
Default Value
""
Remarks
The location of the keyring.
If the keyring is stored in a directory, set this property to the directory. The directory must contain the files "secring.gpg" and "pubring.gpg". A keyring may also be stored in a single file. If the keyring is a file this property should be set to the path of the file.
When This property is set the component will read the keyring and populate the Key* properties with the first key found in the keyring. Set KeyUserId to select a different key in the current keyring.
The RecipientKeyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the RecipientKeyCount property.
This property is not available at design time.
Data Type
String
RecipientKeyUserId Property (PHTMLMailer Component)
The user Id of the key.
Syntax
__property String RecipientKeyUserId[int RecipientKeyIndex] = { read=FRecipientKeyUserId, write=FSetRecipientKeyUserId };
Default Value
""
Remarks
The user Id of the key. When a key is loaded this property is populated with the user Id associated with the key. This property may be set to load a key from the Keyring. When this property is set the component will search the Keyring for a key associated with the UserId specified.
When loading a key with multiple user Ids, this property will be populated with the UserId that was most recently added to the key. To discover all of the UserIds associated with a key query this property and KeyOtherUserIds after loading the key.
The UserId format is:
FirstName LastName (Comment) <Email>Not all values are required when selecting or generating a key, but at least FirstName or Email are required.
When using this property to select a key you may also specify the key's Id, or any of its subkeys' Ids, instead of a user Id. The component will then search for a key with a matching Id. This is helpful in situations where you do not have the UserId but still need to load the key, such as within the OpenPGP component's RecipientInfo event.
The RecipientKeyIndex parameter specifies the index of the item in the array. The size of the array is controlled by the RecipientKeyCount property.
This property is not available at design time.
Data Type
String
ReplyTo Property (PHTMLMailer Component)
A mail address to which to reply (optional).
Syntax
__property String ReplyTo = { read=FReplyTo, write=FSetReplyTo };
Default Value
""
Remarks
If this property contains a non-empty string, a Reply-To SMTP header is created for the message. This header shows the address to use for replies (useful if this address is different from the one in From).
If the resulting header is longer than MaxHeaderLength, then it is folded according to RFC 822 specifications.
Data Type
String
SendTo Property (PHTMLMailer Component)
A comma separated list of addresses for destinations (required).
Syntax
__property String SendTo = { read=FSendTo, write=FSetSendTo };
Default Value
""
Remarks
This property specifies a comma separated list of destinations for the mail message. A copy of the message is sent to each of them, and a To SMTP header is created containing the destination addresses.
Examples of valid addresses are: "Friendly Name" <address@company.com> or address@company.com
The component will fail if the MailServer returns an error code about any email address specified in SendTo or Cc but it will silently ignore the error if the same happens with an email address specified in BCc.
If the resulting header is longer than MaxHeaderLength, then it is folded according to RFC 822 specifications.
NOTE: You must clear the MessageRecipients properties before setting this property to remove previous recipients.
Data Type
String
Sensitivity Property (PHTMLMailer Component)
Sensitivity of the mail message (optional).
Syntax
__property TipgPHTMLMailerSensitivities Sensitivity = { read=FSensitivity, write=FSetSensitivity };
enum TipgPHTMLMailerSensitivities { esUnspecified=0, esPersonal=1, esPrivate=2, esCompanyConfidential=3 };
Default Value
esUnspecified
Remarks
This property is an indication of how sensitive it is to disclose the message to people other than the recipients of the message. When set, a Sensitivity header will added to the message. Possible values are: esPersonal (1), esPrivate (2), and esCompanyConfidential (3).
Data Type
Integer
SigningAlgorithm Property (PHTMLMailer Component)
The signature hash algorithm used when signing.
Syntax
__property String SigningAlgorithm = { read=FSigningAlgorithm, write=FSetSigningAlgorithm };
Default Value
"SHA256"
Remarks
This property specifies the signature hash algorithm used when signing. Possible values are:
- SHA1
- MD5
- SHA256 (default)
- SHA384
- SHA512
- SHA224
- RIPEMD160
Data Type
String
SSLAcceptServerCertEncoded Property (PHTMLMailer Component)
This is the certificate (PEM/base64 encoded).
Syntax
__property String SSLAcceptServerCertEncoded = { read=FSSLAcceptServerCertEncoded, write=FSetSSLAcceptServerCertEncoded }; __property DynamicArray<Byte> SSLAcceptServerCertEncodedB = { read=FSSLAcceptServerCertEncodedB, write=FSetSSLAcceptServerCertEncodedB };
Default Value
""
Remarks
This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLAcceptServerCertStore and SSLAcceptServerCertSubject properties also may be used to specify a certificate.
When SSLAcceptServerCertEncoded is set, a search is initiated in the current SSLAcceptServerCertStore for the private key of the certificate. If the key is found, SSLAcceptServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLAcceptServerCertSubject is set to an empty string.
This property is not available at design time.
Data Type
Byte Array
SSLCertEncoded Property (PHTMLMailer Component)
This is the certificate (PEM/base64 encoded).
Syntax
__property String SSLCertEncoded = { read=FSSLCertEncoded, write=FSetSSLCertEncoded }; __property DynamicArray<Byte> SSLCertEncodedB = { read=FSSLCertEncodedB, write=FSetSSLCertEncodedB };
Default Value
""
Remarks
This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLCertStore and SSLCertSubject properties also may be used to specify a certificate.
When SSLCertEncoded is set, a search is initiated in the current SSLCertStore for the private key of the certificate. If the key is found, SSLCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLCertSubject is set to an empty string.
This property is not available at design time.
Data Type
Byte Array
SSLCertStore Property (PHTMLMailer Component)
This is the name of the certificate store for the client certificate.
Syntax
__property String SSLCertStore = { read=FSSLCertStore, write=FSetSSLCertStore }; __property DynamicArray<Byte> SSLCertStoreB = { read=FSSLCertStoreB, write=FSetSSLCertStoreB };
Default Value
"MY"
Remarks
This is the name of the certificate store for the client certificate.
The SSLCertStoreType property denotes the type of the certificate store specified by SSLCertStore. If the store is password protected, specify the password in SSLCertStorePassword.
SSLCertStore is used in conjunction with the SSLCertSubject property to specify client certificates. If SSLCertStore has a value, and SSLCertSubject or SSLCertEncoded is set, a search for a certificate is initiated. Please see the SSLCertSubject property for details.
Designations of certificate stores are platform dependent.
The following designations are the most common User and Machine certificate stores in Windows:
MY | A certificate store holding personal certificates with their associated private keys. |
CA | Certifying authority certificates. |
ROOT | Root certificates. |
When the certificate store type is PFXFile, this property must be set to the name of the file. When the type is PFXBlob, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).
Data Type
Byte Array
SSLCertStorePassword Property (PHTMLMailer Component)
If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.
Syntax
__property String SSLCertStorePassword = { read=FSSLCertStorePassword, write=FSetSSLCertStorePassword };
Default Value
""
Remarks
If the type of certificate store requires a password, this property is used to specify the password needed to open the certificate store.
Data Type
String
SSLCertStoreType Property (PHTMLMailer Component)
This is the type of certificate store for this certificate.
Syntax
__property TipgPHTMLMailerSSLCertStoreTypes SSLCertStoreType = { read=FSSLCertStoreType, write=FSetSSLCertStoreType };
enum TipgPHTMLMailerSSLCertStoreTypes { cstUser=0, cstMachine=1, cstPFXFile=2, cstPFXBlob=3, cstJKSFile=4, cstJKSBlob=5, cstPEMKeyFile=6, cstPEMKeyBlob=7, cstPublicKeyFile=8, cstPublicKeyBlob=9, cstSSHPublicKeyBlob=10, cstP7BFile=11, cstP7BBlob=12, cstSSHPublicKeyFile=13, cstPPKFile=14, cstPPKBlob=15, cstXMLFile=16, cstXMLBlob=17, cstJWKFile=18, cstJWKBlob=19, cstSecurityKey=20, cstBCFKSFile=21, cstBCFKSBlob=22, cstPKCS11=23, cstAuto=99 };
Default Value
cstUser
Remarks
This is the type of certificate store for this certificate.
The component supports both public and private keys in a variety of formats. When the cstAuto value is used, the component will automatically determine the type. This property can take one of the following values:
0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user.
Note: This store type is not available in Java. |
1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store.
Note: This store type is not available in Java. |
2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. |
3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. |
4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates.
Note: This store type is only available in Java. |
5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format.
Note: this store type is only available in Java. |
6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. |
8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. |
10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. |
11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. |
12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. |
13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. |
14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). |
16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. |
17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. |
18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). |
19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). |
21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store).
Note: This store type is only available in Java and .NET. |
22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format.
Note: This store type is only available in Java and .NET. |
23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface.
To use a security key, the necessary data must first be collected using the CertMgr component. The ListStoreCertificates method may be called after setting CertStoreType to cstPKCS11, CertStorePassword to the PIN, and CertStore to the full path of the PKCS#11 DLL. The certificate information returned in the CertList event's CertEncoded parameter may be saved for later use. When using a certificate, pass the previously saved security key information as the SSLCertStore and set SSLCertStorePassword to the PIN. Code Example. SSH Authentication with Security Key:
|
99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. |
Data Type
Integer
SSLCertSubject Property (PHTMLMailer Component)
This is the subject of the certificate used for client authentication.
Syntax
__property String SSLCertSubject = { read=FSSLCertSubject, write=FSetSSLCertSubject };
Default Value
""
Remarks
This is the subject of the certificate used for client authentication.
This property must be set after all other certificate properties are set. When this property is set, a search is performed in the current certificate store to locate a certificate with a matching subject.
If a matching certificate is found, the property is set to the full subject of the matching certificate.
If an exact match is not found, the store is searched for subjects containing the value of the property.
If a match is still not found, the property is set to an empty string, and no certificate is selected.
The special value "*" picks a random certificate in the certificate store.
The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=support@nsoftware.com". Common fields and their meanings are as follows:
Field | Meaning |
CN | Common Name. This is commonly a hostname like www.server.com. |
O | Organization |
OU | Organizational Unit |
L | Locality |
S | State |
C | Country |
E | Email Address |
If a field value contains a comma, it must be quoted.
Data Type
String
SSLEnabled Property (PHTMLMailer Component)
Whether TLS/SSL is enabled.
Syntax
__property bool SSLEnabled = { read=FSSLEnabled, write=FSetSSLEnabled };
Default Value
False
Remarks
This setting specifies whether TLS/SSL is enabled in the component. When False (default) the component operates in plaintext mode. When True TLS/SSL is enabled.
TLS/SSL may also be enabled by setting SSLStartMode. Setting SSLStartMode will automatically update this property value.
This property is not available at design time.
Data Type
Boolean
SSLProvider Property (PHTMLMailer Component)
This specifies the SSL/TLS implementation to use.
Syntax
__property TipgPHTMLMailerSSLProviders SSLProvider = { read=FSSLProvider, write=FSetSSLProvider };
enum TipgPHTMLMailerSSLProviders { sslpAutomatic=0, sslpPlatform=1, sslpInternal=2 };
Default Value
sslpAutomatic
Remarks
This property specifies the SSL/TLS implementation to use. In most cases the default value of 0 (Automatic) is recommended and should not be changed. When set to 0 (Automatic) the component will select whether to use the platform implementation or the internal implementation depending on the operating system as well as the TLS version being used.
Possible values are:
0 (sslpAutomatic - default) | Automatically selects the appropriate implementation. |
1 (sslpPlatform) | Uses the platform/system implementation. |
2 (sslpInternal) | Uses the internal implementation. |
In most cases using the default value (Automatic) is recommended. The component will select a provider depending on the current platform.
When Automatic is selected the platform implementation is used by default. When TLS 1.3 is enabled via SSLEnabledProtocols the internal implementation is used.
Data Type
Integer
SSLServerCertEncoded Property (PHTMLMailer Component)
This is the certificate (PEM/base64 encoded).
Syntax
__property String SSLServerCertEncoded = { read=FSSLServerCertEncoded }; __property DynamicArray<Byte> SSLServerCertEncodedB = { read=FSSLServerCertEncodedB };
Default Value
""
Remarks
This is the certificate (PEM/Base64 encoded). This property is used to assign a specific certificate. The SSLServerCertStore and SSLServerCertSubject properties also may be used to specify a certificate.
When SSLServerCertEncoded is set, a search is initiated in the current SSLServerCertStore for the private key of the certificate. If the key is found, SSLServerCertSubject is updated to reflect the full subject of the selected certificate; otherwise, SSLServerCertSubject is set to an empty string.
This property is read-only and not available at design time.
Data Type
Byte Array
SSLStartMode Property (PHTMLMailer Component)
Determines how the component starts the SSL negotiation.
Syntax
__property TipgPHTMLMailerSSLStartModes SSLStartMode = { read=FSSLStartMode, write=FSetSSLStartMode };
enum TipgPHTMLMailerSSLStartModes { sslAutomatic=0, sslImplicit=1, sslExplicit=2, sslNone=3 };
Default Value
sslNone
Remarks
The SSLStartMode property may have one of the following values:
0 (sslAutomatic) | If the remote port is set to the standard plaintext port of the protocol (where applicable), the component will behave the same as if SSLStartMode is set to sslExplicit. In all other cases, SSL negotiation will be implicit (sslImplicit). |
1 (sslImplicit) | The SSL negotiation will start immediately after the connection is established. |
2 (sslExplicit) | The component will first connect in plaintext, and then explicitly start SSL negotiation through a protocol command such as STARTTLS. |
3 (sslNone - default) | No SSL negotiation, no SSL security. All communication will be in plaintext mode. |
Data Type
Integer
Subject Property (PHTMLMailer Component)
The subject of the mail message (optional).
Syntax
__property String Subject = { read=FSubject, write=FSetSubject };
Default Value
""
Remarks
The string in this property is sent with a Subject SMTP header to the mail recipient.
If the resulting header is longer than MaxHeaderLength, then it is folded according to RFC 822 specifications.
Data Type
String
Timeout Property (PHTMLMailer Component)
A timeout for the component.
Syntax
__property int Timeout = { read=FTimeout, write=FSetTimeout };
Default Value
60
Remarks
If the Timeout property is set to 0, all operations will run uninterrupted until successful completion or an error condition is encountered.
If Timeout is set to a positive value, the component will wait for the operation to complete before returning control.
The component will use DoEvents to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not "freeze" and remains responsive.
If Timeout expires, and the operation is not yet complete, the component raises an exception.
Please note that by default, all timeouts are inactivity timeouts, i.e. the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.
The default value for the Timeout property is 60 seconds.
Data Type
Integer
User Property (PHTMLMailer Component)
A user identifier to login as in the MailServer .
Syntax
__property String User = { read=FUser, write=FSetUser };
Default Value
""
Remarks
If this property is set to a non-empty string, then when connecting to the MailServer an AUTH or CRAM-MD5 (depending on the value of AuthMechanism) command is sent in order to provide authentication information for the user.
This property is not available at design time.
Data Type
String
AddAttachment Method (PHTMLMailer Component)
This adds FileName as an attachment.
Syntax
void __fastcall AddAttachment(String FileName);
Remarks
This method adds the file name as an attachment. The full list of attachments is contained in the Attachments property.
Example 1: Adding an Attachment
component.AddAttachment("C:\file1.zip");
component.AddAttachment("C:\file2.zip");
component.Send();
Example 3: Using an Attachments Array
component.AttachmentCount = 1;
component.AttachmentName(0) = "name";
component.AttachmentFile(0) = "C:\file.txt";
Config Method (PHTMLMailer Component)
Sets or retrieves a configuration setting.
Syntax
String __fastcall 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.
Connect Method (PHTMLMailer Component)
This method connects to the mail relay and sends the SMTP HELO command.
Syntax
void __fastcall Connect();
Remarks
This method connects to the mail relay and sends the SMTP HELO command, thus preparing to send messages. Any number of messages can later be sent using the Send method.
Example. Connecting and Sending an Email:
control.MailServer = "MyServer"
control.From = "me@server.com"
control.SendTo = "recipient@server.com"
control.Subject = "My Subject"
control.MessageText = "This is the message body"
control.Connect()
control.Send()
control.Disconnect()
Disconnect Method (PHTMLMailer Component)
This method disconnects from the SMTP server.
Syntax
void __fastcall Disconnect();
Remarks
This method disconnects from the mail relay.
DoEvents Method (PHTMLMailer Component)
Processes events from the internal message queue.
Syntax
void __fastcall DoEvents();
Remarks
When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns.
Encrypt Method (PHTMLMailer Component)
Encrypts the message.
Syntax
void __fastcall Encrypt();
Remarks
This method encrypts the specified message.
The message is encrypted with the public keys specified in the RecipientKey* properties.
When encrypting, the following properties may be used to further configure the component:
Interrupt Method (PHTMLMailer Component)
Interrupt the current method.
Syntax
void __fastcall Interrupt();
Remarks
If there is no method in progress, Interrupt simply returns, doing nothing.
ProcessQueue Method (PHTMLMailer Component)
Sends the messages which have previously been queued into QueueDir .
Syntax
void __fastcall ProcessQueue(String QueueDir);
Remarks
This method sends the messages which have previously been queued into QueueDir. The PITrail event shows the interaction with the server as messages as are processed.
This method looks in the directory for files with extension ".queued" and starts processing them.
When processing starts, the file extension is changed to ".sending". If an error happens at this stage, the sending process is aborted, and the file extension is changed to ".failed".
If the file is successfully sent, the file is normally deleted, unless the KeepQueue configuration setting is set to True, in which case the file extension is instead changed to ".sent" and the queue file is not deleted.
Queue Method (PHTMLMailer Component)
Queues the message into QueueDir .
Syntax
String __fastcall Queue(String QueueDir);
Remarks
This method queues the message into QueueDir. The message is queued into a unique file into the directory QueueDir for future processing.
QueueDir must already exist, or an error will be generated. Alternatively, QueueDir may be set to "*" to return the result as a string instead of writing it to a file.
The method returns the name of the unique queue file created in QueueDir. The file extension is ".queued".
Please refer to the ProcessQueue method for more information on email queue processing.
ResetHeaders Method (PHTMLMailer Component)
Resets all the message headers to empty.
Syntax
void __fastcall ResetHeaders();
Remarks
This method resets all the message headers to "" (empty string). Use this method before creating a new message, so that headers from the previous message are not carried over to the next one.
Send Method (PHTMLMailer Component)
This method sends the current message and MIME-encoded attachment.
Syntax
void __fastcall Send();
Remarks
This method sends the current message and MIME-encoded attachment. If the component is not connected to the mail relay, a connection is created, the message is sent, and then the connection is closed unless an error occurs.
If the component is already connected (by use of the Connect method), the connection will remain open after the message is sent. To disconnect, call the Disconnect method.
Example. Send an HTML Email:
HTMLMailerControl.MailServer = "myserver"
HTMLMailerControl.SendTo = "recipient@myserver.com"
HTMLMailerControl.From = "me@myserver.com"
HTMLMailerControl.Subject = "My Subject"
HTMLMailerControl.MessageHTML = "<b>Hello</b>, my name is <i>Tom</i>"
HTMLMailerControl.Send
Sign Method (PHTMLMailer Component)
Signs the message.
Syntax
void __fastcall Sign();
Remarks
This method signs the specified message.
The message is signed with the private key specified in the Key* properties.
When signing, the following properties may be used to further configure the component:
SignAndEncrypt Method (PHTMLMailer Component)
Signs and encrypts the current message.
Syntax
void __fastcall SignAndEncrypt();
Remarks
This method signs and encrypts the specified message.
The message is encrypted with the public keys specified in the RecipientKey* properties and signed with the private key specified in the Key* properties.
When encrypting, the following properties may be used to further configure the component:
When signing, the following properties may be used to further configure the component:
ConnectionStatus Event (PHTMLMailer Component)
This event is fired to indicate changes in the connection state.
Syntax
typedef struct { String ConnectionEvent; int StatusCode; String Description; } TipgPHTMLMailerConnectionStatusEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerConnectionStatusEvent)(System::TObject* Sender, TipgPHTMLMailerConnectionStatusEventParams *e); __property TipgPHTMLMailerConnectionStatusEvent OnConnectionStatus = { read=FOnConnectionStatus, write=FOnConnectionStatus };
Remarks
The ConnectionStatus event is fired when the connection state changes: for example, completion of a firewall or proxy connection or completion of a security handshake.
The ConnectionEvent parameter indicates the type of connection event. Values may include the following:
Firewall connection complete. | |
Secure Sockets Layer (SSL) or S/Shell handshake complete (where applicable). | |
Remote host connection complete. | |
Remote host disconnected. | |
SSL or S/Shell connection broken. | |
Firewall host disconnected. |
EndTransfer Event (PHTMLMailer Component)
This event is fired when the message text completes transferring.
Syntax
typedef struct { int Direction; } TipgPHTMLMailerEndTransferEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerEndTransferEvent)(System::TObject* Sender, TipgPHTMLMailerEndTransferEventParams *e); __property TipgPHTMLMailerEndTransferEvent OnEndTransfer = { read=FOnEndTransfer, write=FOnEndTransfer };
Remarks
If MessageText is not empty, the EndTransfer event is fired when the MessageText finishes transferring from the local host to the MailServer. If MessageText is empty, the event is not fired.
If a file is attached to the MessageText via the AttachedFile property, then EndTransfer fires again when the file finishes transferring. For more information, go to the description of the AttachedFile property.
The Direction parameter shows whether the client (0) or the server (1) is sending the data.
Error Event (PHTMLMailer Component)
Information about errors during data delivery.
Syntax
typedef struct { int ErrorCode; String Description; } TipgPHTMLMailerErrorEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerErrorEvent)(System::TObject* Sender, TipgPHTMLMailerErrorEventParams *e); __property TipgPHTMLMailerErrorEvent OnError = { read=FOnError, write=FOnError };
Remarks
The Error event is fired in case of exceptional conditions during message processing. Normally the component raises 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.
KeyPassphrase Event (PHTMLMailer Component)
Fired if the passphrase of current key is incorrect or empty.
Syntax
typedef struct { String UserId; String KeyId; String Passphrase; } TipgPHTMLMailerKeyPassphraseEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerKeyPassphraseEvent)(System::TObject* Sender, TipgPHTMLMailerKeyPassphraseEventParams *e); __property TipgPHTMLMailerKeyPassphraseEvent OnKeyPassphrase = { read=FOnKeyPassphrase, write=FOnKeyPassphrase };
Remarks
This event fires when the passphrase for the key is required. The passphrase must be specified before operations requiring the secret key are attempted. The passphrase may be supplied by setting the Passphrase parameter in this event, or by specifying the KeyPassphrase property before attempting the operation.
The passphrase is required when using the following methods in KeyMgr:
- AddUserId
- SignUserId
- ChangeExpirationDate
- ChangePassphrase
When using the OpenPGP component, or an email-based component, the following methods require a passphrase for the key:
- Decrypt
- Sign
- SignAndEncrypt
PITrail Event (PHTMLMailer Component)
Traces the commands sent to the mail server, and the respective replies.
Syntax
typedef struct { int Direction; String Message; } TipgPHTMLMailerPITrailEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerPITrailEvent)(System::TObject* Sender, TipgPHTMLMailerPITrailEventParams *e); __property TipgPHTMLMailerPITrailEvent OnPITrail = { read=FOnPITrail, write=FOnPITrail };
Remarks
The PITrail event is useful for debugging purposes. It shows all the interaction between the client and the server, line by line, except for message header and body transfers.
The Message parameter contains the full text of the message. The Direction parameter shows the originator of the message:
0 (Client) | The Message originates from the client. |
1 (Server) | The Message originates from the server. |
2 (Info) | The Message is an informative message originating from the client software (the component code). |
Progress Event (PHTMLMailer Component)
Fired as progress is made.
Syntax
typedef struct { __int64 BytesProcessed; int PercentProcessed; } TipgPHTMLMailerProgressEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerProgressEvent)(System::TObject* Sender, TipgPHTMLMailerProgressEventParams *e); __property TipgPHTMLMailerProgressEvent OnProgress = { read=FOnProgress, write=FOnProgress };
Remarks
This event is fired automatically as data is processed by the component.
The PercentProcessed parameter indicates the current status of the operation.
The BytesProcessed parameter holds the total number of bytes processed so far.
SSLServerAuthentication Event (PHTMLMailer Component)
Fired after the server presents its certificate to the client.
Syntax
typedef struct { String CertEncoded; DynamicArray<Byte> CertEncodedB; String CertSubject; String CertIssuer; String Status; bool Accept; } TipgPHTMLMailerSSLServerAuthenticationEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerSSLServerAuthenticationEvent)(System::TObject* Sender, TipgPHTMLMailerSSLServerAuthenticationEventParams *e); __property TipgPHTMLMailerSSLServerAuthenticationEvent OnSSLServerAuthentication = { read=FOnSSLServerAuthentication, write=FOnSSLServerAuthentication };
Remarks
During this event, the client can decide whether or not to continue with the connection process. The Accept parameter is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether or not to continue.
When Accept is False, Status shows why the verification failed (otherwise, Status contains the string OK). If it is decided to continue, you can override and accept the certificate by setting the Accept parameter to True.
SSLStatus Event (PHTMLMailer Component)
Shows the progress of the secure connection.
Syntax
typedef struct { String Message; } TipgPHTMLMailerSSLStatusEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerSSLStatusEvent)(System::TObject* Sender, TipgPHTMLMailerSSLStatusEventParams *e); __property TipgPHTMLMailerSSLStatusEvent OnSSLStatus = { read=FOnSSLStatus, write=FOnSSLStatus };
Remarks
The event is fired for informational and logging purposes only. This event tracks the progress of the connection.
StartTransfer Event (PHTMLMailer Component)
Fired when the message text starts transferring.
Syntax
typedef struct { int Direction; } TipgPHTMLMailerStartTransferEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerStartTransferEvent)(System::TObject* Sender, TipgPHTMLMailerStartTransferEventParams *e); __property TipgPHTMLMailerStartTransferEvent OnStartTransfer = { read=FOnStartTransfer, write=FOnStartTransfer };
Remarks
If MessageText is not empty, the StartTransfer event is fired when the MessageText starts transferring from the local host to the MailServer. If MessageText is empty, the event is not fired.
If a file is attached to the MessageText via the AttachedFile property, then StartTransfer fires again when the file starts transferring. Please go to the description of the AttachedFile property for more information.
The Direction parameter shows whether the client (0) or the server (1) is sending the data.
Status Event (PHTMLMailer Component)
Shows the progress of the operation.
Syntax
typedef struct { String Message; } TipgPHTMLMailerStatusEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerStatusEvent)(System::TObject* Sender, TipgPHTMLMailerStatusEventParams *e); __property TipgPHTMLMailerStatusEvent OnStatus = { read=FOnStatus, write=FOnStatus };
Remarks
The event is fired for informational and logging purposes only. It may be used to track the progress of an operation.
The level of detail is controlled by the LogLevel setting.
Transfer Event (PHTMLMailer Component)
Fired while the message text gets transferred to MailServer .
Syntax
typedef struct { int Direction; __int64 BytesTransferred; int PercentDone; String Text; DynamicArray<Byte> TextB; } TipgPHTMLMailerTransferEventParams; typedef void __fastcall (__closure *TipgPHTMLMailerTransferEvent)(System::TObject* Sender, TipgPHTMLMailerTransferEventParams *e); __property TipgPHTMLMailerTransferEvent OnTransfer = { read=FOnTransfer, write=FOnTransfer };
Remarks
One or more Transfer events are fired during message delivery. Messages consist of MessageText and an optional AttachedFile. The BytesTransferred parameter shows the number of bytes sent starting from the beginning of MessageText and/or AttachedFile.
Text contains the current portion of the message being sent.
The Direction parameter shows whether the client (0) or the server (1) is sending the data.
The PercentDone parameter shows the progress of the transfer in the corresponding direction. If PercentDone can not be calculated the value will be -1.
Note: Events are not re-entrant. Performing time-consuming operations within this event will prevent it from firing again in a timely manner and may affect overall performance.
Config Settings (PHTMLMailer 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.PHTMLMailer Config Settings
Note: some mail applications such as GpgOL cannot process cleartext signatures.
zlib | 1-6 |
zip | 1-6 |
bzip2 | 1-9 |
DSA Notes
DSA requires that the hash be 160 bits or larger, which means MD5 is not a suitable algorithm. When DSA Signature Hash Algorithm selection is enabled (default) the component will use the preferred algorithm from the key if it meets the requirements for DSA. If the preferred algorithm is MD5 and does not meed the requirements for DSA the component will automatically use a suitable algorithm based on the Q element of the DSA key (may be SHA1, SHA224, or SHA256).
ECDSA Notes
The ECDSA Signature Hash Algorithm requirements are directly related to the KeyCurve used by the key. When this setting is enabled (default) the component will use the preferred algorithm from the key if it meets the requirements for ECDSA. If the preferred algorithm does not meet the requirements the component will automatically select a valid hash algorithm based on the curve as follows:
Curve | Hash Algorithm |
secp256r1 | SHA256 |
secp384r1 | SHA384 |
secp521r1 | SHA512 |
secp256k1 | SHA256 |
0 (None) | No events are logged. |
1 (Info - default) | Informational events are logged. |
2 (Verbose) | Detailed data is logged. |
3 (Debug) | Debug data is logged. |
This setting will be populated after calling Decrypt, VerifySignature, or DecryptAndVerifySignature.
HTMLMailer Config Settings
0 | 7-bit |
1 | Quoted-Printable |
2 | Base64 |
3 | 8-bit |
0 | 7-bit |
1 | Quoted-Printable |
2 | Base64 |
3 | 8-bit |
Note: Be aware of security considerations when using this configuration.
SMTP Config Settings
Bearer ya29.AHES6ZRmS-8xPbpGetC1VbABJIBRdKm-c4X7wMVGAbgxdGt5q8Ts3Q
Note: When using amXOAUTH2, User must be specified, but Password is not required.
If AllowExtensions is True the EHLO command will be sent instead of the HELO command.
It is generally a good idea to use a MaxHeaderLength of less than 100 bytes, although different mail relays and mail servers have different requirements for header lengths.
As an example:
smtp1.Send();
string rawMsg = smtp1.Config("MessageHeadersString") + smtp1.Config("TransferText");
Possible values are:
- "MD5"
- "SHA1" (default)
- "SHA256"
As an example:
smtp1.Send();
string rawMsg = smtp1.Config("MessageHeadersString") + smtp1.Config("TransferText");
TCPClient Config Settings
If the FirewallHost setting is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, the FirewallHost setting is set to the corresponding address. If the search is not successful, an error is returned.
Note: This setting is provided for use by components that do not directly expose Firewall properties.
Note: This setting is provided for use by components that do not directly expose Firewall properties.
Note: This configuration setting is provided for use by components that do not directly expose Firewall properties.
0 | No firewall (default setting). |
1 | Connect through a tunneling proxy. FirewallPort is set to 80. |
2 | Connect through a SOCKS4 Proxy. FirewallPort is set to 1080. |
3 | Connect through a SOCKS5 Proxy. FirewallPort is set to 1080. |
10 | Connect through a SOCKS4A Proxy. FirewallPort is set to 1080. |
Note: This setting is provided for use by components that do not directly expose Firewall properties.
Note: This setting is provided for use by components that do not directly expose Firewall properties.
Note: This value is not applicable in macOS.
In the case that Linger is True (default), two scenarios determine how long the connection will linger. In the first, if LingerTime is 0 (default), the system will attempt to send pending data for a connection until the default IP timeout expires.
In the second scenario, if LingerTime is a positive value, the system will attempt to send pending data until the specified LingerTime is reached. If this attempt fails, then the system will reset the connection.
The default behavior (which is also the default mode for stream sockets) might result in a long delay in closing the connection. Although the component returns control immediately, the system could hold system resources until all pending data are sent (even after your application closes).
Setting this property to False forces an immediate disconnection. If you know that the other side has received all the data you sent (e.g., by a client acknowledgment), setting this property to False might be the appropriate course of action.
In multi-homed hosts (machines with more than one IP interface) setting LocalHost to the value of an interface will make the component initiate connections (or accept in the case of server components) only through that interface.
If the component is connected, the LocalHost setting shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multi-homed hosts (machines with more than one IP interface).
Setting this to 0 (default) enables the system to choose a port at random. The chosen port will be shown by LocalPort after the connection is established.
LocalPort cannot be changed once a connection is made. Any attempt to set this when a connection is active will generate an error.
This; setting is useful when trying to connect to services that require a trusted port in the client side. An example is the remote shell (rsh) service in UNIX systems.
If an EOL string is found in the input stream before MaxLineLength bytes are received, the DataIn event is fired with the EOL parameter set to True, and the buffer is reset.
If no EOL is found, and MaxLineLength bytes are accumulated in the buffer, the DataIn event is fired with the EOL parameter set to False, and the buffer is reset.
The minimum value for MaxLineLength is 256 bytes. The default value is 2048 bytes.
www.google.com;www.nsoftware.com
Note: This value is not applicable in Java.
By default, this config is set to false.
0 | IPv4 Only |
1 | IPv6 Only |
2 | IPv6 with IPv4 fallback |
SSL Config Settings
When enabled, SSL packet logs are output using the SSLStatus event, which will fire each time an SSL packet is sent or received.
Enabling this setting has no effect if SSLProvider is set to Platform.
The path set by this property should point to a directory containing CA certificates in PEM format. The files each contain one CA certificate. The files are looked up by the CA subject name hash value, which must hence be available. If more than one CA certificate with the same name hash value exist, the extension must be different (e.g. 9d66eef0.0, 9d66eef0.1 etc). OpenSSL recommends to use the c_rehash utility to create the necessary links. Please refer to the OpenSSL man page SSL_CTX_load_verify_locations(3) for details.
The file set by this property should contain a list of CA certificates in PEM format. The file can contain several CA certificates identified by
-----BEGIN CERTIFICATE-----
... (CA certificate in base64 encoding) ...
-----END CERTIFICATE-----
sequences. Before, between, and after the certificates text is allowed which can be used e.g. for descriptions of the certificates. Please refer to the OpenSSL man page SSL_CTX_load_verify_locations(3) for details.
The format of this string is described in the OpenSSL man page ciphers(1) section "CIPHER LIST FORMAT". Please refer to it for details. The default string "DEFAULT" is determined at compile time and is normally equivalent to "ALL:!ADH:RC4+RSA:+SSLv2:@STRENGTH".
By default OpenSSL uses the device file "/dev/urandom" to seed the PRNG and setting OpenSSLPrngSeedData is not required. If set, the string specified is used to seed the PRNG.
If set to true, the component will reuse the context if and only if the following criteria are met:
- The target host name is the same.
- The system cache entry has not expired (default timeout is 10 hours).
- The application process that calls the function is the same.
- The logon session is the same.
- The instance of the component is the same.
-----BEGIN CERTIFICATE----- MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw ... eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w F0I1XhM+pKj7FjDr+XNj -----END CERTIFICATE----- \r \n -----BEGIN CERTIFICATE----- MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp .. d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA -----END CERTIFICATE-----
When set to 0 (default) the CRL check will not be performed by the component. When set to 1, it will attempt to perform the CRL check, but will continue without an error if the server's certificate does not support CRL. When set to 2, it will perform the CRL check and will throw an error if CRL is not supported.
This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems.
When set to 0 (default) the component will not perform an OCSP check. When set to 1, it will attempt to perform the OCSP check, but will continue without an error if the server's certificate does not support OCSP. When set to 2, it will perform the OCSP check and will throw an error if OCSP is not supported.
This configuration setting is only supported in the Java, C#, and C++ editions. In the C++ edition, it is only supported on Windows operating systems.
Please note that this setting contains the minimum cipher strength requested from the security library. The actual cipher strength used for the connection is shown by the SSLStatus event.
Use this setting with caution. Requesting a lower cipher strength than necessary could potentially cause serious security vulnerabilities in your application.
When the provider is OpenSSL, SSLCipherStrength is currently not supported. This functionality is instead made available through the OpenSSLCipherList config setting.
By default, the enabled cipher suites will include all available ciphers ("*").
The special value "*" means that the component will pick all of the supported cipher suites. If SSLEnabledCipherSuites is set to any other value, only the specified cipher suites will be considered.
Multiple cipher suites are separated by semicolons.
Example values when SSLProvider is set to Platform:
obj.config("SSLEnabledCipherSuites=*");
obj.config("SSLEnabledCipherSuites=CALG_AES_256");
obj.config("SSLEnabledCipherSuites=CALG_AES_256;CALG_3DES");
Possible values when SSLProvider is set to Platform include:
- CALG_3DES
- CALG_3DES_112
- CALG_AES
- CALG_AES_128
- CALG_AES_192
- CALG_AES_256
- CALG_AGREEDKEY_ANY
- CALG_CYLINK_MEK
- CALG_DES
- CALG_DESX
- CALG_DH_EPHEM
- CALG_DH_SF
- CALG_DSS_SIGN
- CALG_ECDH
- CALG_ECDH_EPHEM
- CALG_ECDSA
- CALG_ECMQV
- CALG_HASH_REPLACE_OWF
- CALG_HUGHES_MD5
- CALG_HMAC
- CALG_KEA_KEYX
- CALG_MAC
- CALG_MD2
- CALG_MD4
- CALG_MD5
- CALG_NO_SIGN
- CALG_OID_INFO_CNG_ONLY
- CALG_OID_INFO_PARAMETERS
- CALG_PCT1_MASTER
- CALG_RC2
- CALG_RC4
- CALG_RC5
- CALG_RSA_KEYX
- CALG_RSA_SIGN
- CALG_SCHANNEL_ENC_KEY
- CALG_SCHANNEL_MAC_KEY
- CALG_SCHANNEL_MASTER_HASH
- CALG_SEAL
- CALG_SHA
- CALG_SHA1
- CALG_SHA_256
- CALG_SHA_384
- CALG_SHA_512
- CALG_SKIPJACK
- CALG_SSL2_MASTER
- CALG_SSL3_MASTER
- CALG_SSL3_SHAMD5
- CALG_TEK
- CALG_TLS1_MASTER
- CALG_TLS1PRF
obj.config("SSLEnabledCipherSuites=*");
obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA");
obj.config("SSLEnabledCipherSuites=TLS_DHE_DSS_WITH_AES_128_CBC_SHA;TLS_DH_ANON_WITH_AES_128_CBC_SHA");
Possible values when SSLProvider is set to Internal include:
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_RSA_WITH_AES_256_GCM_SHA384
- TLS_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDH_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_DSS_WITH_AES_256_GCM_SHA384
- TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDH_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDH_RSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_DHE_DSS_WITH_AES_128_GCM_SHA256
- TLS_DH_RSA_WITH_AES_128_GCM_SHA256 (Not Recommended)
- TLS_DH_RSA_WITH_AES_256_GCM_SHA384 (Not Recommended)
- TLS_DH_DSS_WITH_AES_128_GCM_SHA256 (Not Recommended)
- TLS_DH_DSS_WITH_AES_256_GCM_SHA384 (Not Recommended)
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
- TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA384
- TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
- TLS_RSA_WITH_AES_256_CBC_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
- TLS_ECDH_RSA_WITH_AES_256_CBC_SHA384
- TLS_DHE_RSA_WITH_AES_256_CBC_SHA256
- TLS_DHE_RSA_WITH_AES_128_CBC_SHA256
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
- TLS_RSA_WITH_AES_128_CBC_SHA256
- TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA256
- TLS_ECDH_RSA_WITH_AES_128_CBC_SHA256
- TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
- TLS_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDH_ECDSA_WITH_AES_256_CBC_SHA
- TLS_DHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDH_RSA_WITH_AES_256_CBC_SHA
- TLS_DHE_DSS_WITH_AES_256_CBC_SHA
- TLS_RSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
- TLS_ECDH_ECDSA_WITH_AES_128_CBC_SHA
- TLS_ECDH_RSA_WITH_AES_128_CBC_SHA
- TLS_DHE_RSA_WITH_AES_128_CBC_SHA
- TLS_DHE_DSS_WITH_AES_128_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA
- TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA
- TLS_ECDH_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_DES_CBC_SHA
- TLS_DHE_RSA_WITH_DES_CBC_SHA
- TLS_DHE_DSS_WITH_DES_CBC_SHA
- TLS_RSA_WITH_RC4_128_MD5
- TLS_RSA_WITH_RC4_128_SHA
When TLS 1.3 is negotiated (see SSLEnabledProtocols) only the following cipher suites are supported:
- TLS_AES_256_GCM_SHA384
- TLS_CHACHA20_POLY1305_SHA256
- TLS_AES_128_GCM_SHA256
SSLEnabledCipherSuites is used together with SSLCipherStrength.
Not all supported protocols are enabled by default (the value of this setting is 4032). If you want more granular control over the enabled protocols, you can set this property to the binary 'OR' of one or more of the following values:
TLS1.3 | 12288 (Hex 3000) |
TLS1.2 | 3072 (Hex C00) (Default) |
TLS1.1 | 768 (Hex 300) (Default) |
TLS1 | 192 (Hex C0) (Default) |
SSL3 | 48 (Hex 30) [Platform Only] |
SSL2 | 12 (Hex 0C) [Platform Only] |
SSLEnabledProtocols - TLS 1.3 Notes
By default when TLS 1.3 is enabled the component will use the internal TLS implementation when the SSLProvider is set to Automatic for all editions.
In editions which are designed to run on Windows SSLProvider can be set to Platform to use the platform implementation instead of the internal implementation. When configured in this manner, please note that the platform provider is only supported on Windows 11 / Windows Server 2022 and up. The default internal provider is available on all platforms and is not restricted to any specific OS version.
If set to 1 (Platform provider) please be aware of the following notes:
- The platform provider is only available on Windows 11 / Windows Server 2022 and up.
- SSLEnabledCipherSuites and other similar SSL configuration settings are not supported.
- If SSLEnabledProtocols includes both TLS 1.3 and TLS 1.2 the above restrictions are still applicable even if TLS 1.2 is negotiated. Enabling TLS 1.3 with the platform provider changes the implementation used for all TLS versions.
SSLEnabledProtocols: SSL2 and SSL3 Notes:
SSL 2.0 and 3.0 are not supported by the component when the SSLProvider is set to internal. To use SSL 2.0 or SSL 3.0, the platform security API must have the protocols enabled and SSLProvider needs to be set to platform.
This setting is only applicable when SSLProvider is set to Internal.
If set to True all certificates returned by the server will be present in the Encoded parameter of the SSLServerAuthentication event. This includes the leaf certificate, any intermediate certificate, and the root certificate.
When set, the component will save the session secrets in the same format as the SSLKEYLOGFILE environment variable functionality used by most major browsers and tools such as Chrome, Firefox, and cURL. This file can then be used in tools such as Wireshark to decrypt TLS traffice for debugging purposes. When writing to this file the component will only append, it will not overwrite previous values.
Note: This setting is only applicable when SSLProvider is set to Internal.
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedCipher[connId]");
Note: For server components (e.g.TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedCipherStrength[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedCipherSuite[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedKeyExchange[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedKeyExchangeStrength[connId]");
Note: For server components (e.g. TCPServer) this is a per-connection setting accessed by passing the ConnectionId. For example:
server.Config("SSLNegotiatedVersion[connId]");
0x00000001 | Ignore time validity status of certificate. |
0x00000002 | Ignore time validity status of CTL. |
0x00000004 | Ignore non-nested certificate times. |
0x00000010 | Allow unknown Certificate Authority. |
0x00000020 | Ignore wrong certificate usage. |
0x00000100 | Ignore unknown certificate revocation status. |
0x00000200 | Ignore unknown CTL signer revocation status. |
0x00000400 | Ignore unknown Certificate Authority revocation status. |
0x00000800 | Ignore unknown Root revocation status. |
0x00008000 | Allow test Root certificate. |
0x00004000 | Trust test Root certificate. |
0x80000000 | Ignore non-matching CN (certificate CN not-matching server name). |
This functionality is currently not available when the provider is OpenSSL.
The value of this setting is a newline (CrLf) separated list of certificates. For instance:
-----BEGIN CERTIFICATE----- MIIEKzCCAxOgAwIBAgIRANTET4LIkxdH6P+CFIiHvTowDQYJKoZIhvcNAQELBQAw ... eWHV5OW1K53o/atv59sOiW5K3crjFhsBOd5Q+cJJnU+SWinPKtANXMht+EDvYY2w F0I1XhM+pKj7FjDr+XNj -----END CERTIFICATE----- \r \n -----BEGIN CERTIFICATE----- MIIEFjCCAv6gAwIBAgIQetu1SMxpnENAnnOz1P+PtTANBgkqhkiG9w0BAQUFADBp .. d8q23djXZbVYiIfE9ebr4g3152BlVCHZ2GyPdjhIuLeH21VbT/dyEHHA -----END CERTIFICATE-----
When specified the component will verify that the server certificate signature algorithm is among the values specified in this setting. If the server certificate signature algorithm is unsupported the component raises an exception.
The format of this value is a comma separated list of hash-signature combinations. For instance:
component.SSLProvider = TCPClientSSLProviders.sslpInternal;
component.Config("SSLEnabledProtocols=3072"); //TLS 1.2
component.Config("TLS12SignatureAlgorithms=sha256-rsa,sha256-dsa,sha1-rsa,sha1-dsa");
The default value for this setting is sha512-ecdsa,sha512-rsa,sha512-dsa,sha384-ecdsa,sha384-rsa,sha384-dsa,sha256-ecdsa,sha256-rsa,sha256-dsa,sha224-ecdsa,sha224-rsa,sha224-dsa,sha1-ecdsa,sha1-rsa,sha1-dsa.
In order to not restrict the server's certificate signature algorithm, specify an empty string as the value for this setting, which will cause the signature_algorithms TLS 1.2 extension to not be sent.
The default value is ecdhe_secp256r1,ecdhe_secp384r1,ecdhe_secp521r1.
When using TLS 1.2 and SSLProvider is set to Internal, the values refer to the supported groups for ECC. The following values are supported:
- "ecdhe_secp256r1" (default)
- "ecdhe_secp384r1" (default)
- "ecdhe_secp521r1" (default)
The default value is set to balance common supported groups and the computational resources required to generate key shares. As a result only some groups are included by default in this setting.
Note: All supported groups can always be used during the handshake even if not listed here, but if a group is used which is not present in this list it will incur an additional round trip and time to generate the key share for that group.
In most cases this setting does not need to be modified. This should only be modified if there is a specific reason to do so.
The default value is ecdhe_x25519,ecdhe_secp256r1,ecdhe_secp384r1,ffdhe_2048,ffdhe_3072
The values are ordered from most preferred to least preferred. The following values are supported:
- "ecdhe_x25519" (default)
- "ecdhe_x448"
- "ecdhe_secp256r1" (default)
- "ecdhe_secp384r1" (default)
- "ecdhe_secp521r1"
- "ffdhe_2048" (default)
- "ffdhe_3072" (default)
- "ffdhe_4096"
- "ffdhe_6144"
- "ffdhe_8192"
- "ed25519" (default)
- "ed448" (default)
- "ecdsa_secp256r1_sha256" (default)
- "ecdsa_secp384r1_sha384" (default)
- "ecdsa_secp521r1_sha512" (default)
- "rsa_pkcs1_sha256" (default)
- "rsa_pkcs1_sha384" (default)
- "rsa_pkcs1_sha512" (default)
- "rsa_pss_sha256" (default)
- "rsa_pss_sha384" (default)
- "rsa_pss_sha512" (default)
The default value is ecdhe_x25519,ecdhe_x448,ecdhe_secp256r1,ecdhe_secp384r1,ecdhe_secp521r1,ffdhe_2048,ffdhe_3072,ffdhe_4096,ffdhe_6144,ffdhe_8192
The values are ordered from most preferred to least preferred. The following values are supported:
- "ecdhe_x25519" (default)
- "ecdhe_x448" (default)
- "ecdhe_secp256r1" (default)
- "ecdhe_secp384r1" (default)
- "ecdhe_secp521r1" (default)
- "ffdhe_2048" (default)
- "ffdhe_3072" (default)
- "ffdhe_4096" (default)
- "ffdhe_6144" (default)
- "ffdhe_8192" (default)
Socket Config Settings
Note: This option is not valid for UDP ports.
Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated the InBufferSize reverts to its defined size. The same happens if you attempt to make it too large or too small.
Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated the OutBufferSize reverts to its defined size. The same happens if you attempt to make it too large or too small.
Base Config Settings
The following is a list of valid code page identifiers:
Identifier | Name |
037 | IBM EBCDIC - U.S./Canada |
437 | OEM - United States |
500 | IBM EBCDIC - International |
708 | Arabic - ASMO 708 |
709 | Arabic - ASMO 449+, BCON V4 |
710 | Arabic - Transparent Arabic |
720 | Arabic - Transparent ASMO |
737 | OEM - Greek (formerly 437G) |
775 | OEM - Baltic |
850 | OEM - Multilingual Latin I |
852 | OEM - Latin II |
855 | OEM - Cyrillic (primarily Russian) |
857 | OEM - Turkish |
858 | OEM - Multilingual Latin I + Euro symbol |
860 | OEM - Portuguese |
861 | OEM - Icelandic |
862 | OEM - Hebrew |
863 | OEM - Canadian-French |
864 | OEM - Arabic |
865 | OEM - Nordic |
866 | OEM - Russian |
869 | OEM - Modern Greek |
870 | IBM EBCDIC - Multilingual/ROECE (Latin-2) |
874 | ANSI/OEM - Thai (same as 28605, ISO 8859-15) |
875 | IBM EBCDIC - Modern Greek |
932 | ANSI/OEM - Japanese, Shift-JIS |
936 | ANSI/OEM - Simplified Chinese (PRC, Singapore) |
949 | ANSI/OEM - Korean (Unified Hangul Code) |
950 | ANSI/OEM - Traditional Chinese (Taiwan; Hong Kong SAR, PRC) |
1026 | IBM EBCDIC - Turkish (Latin-5) |
1047 | IBM EBCDIC - Latin 1/Open System |
1140 | IBM EBCDIC - U.S./Canada (037 + Euro symbol) |
1141 | IBM EBCDIC - Germany (20273 + Euro symbol) |
1142 | IBM EBCDIC - Denmark/Norway (20277 + Euro symbol) |
1143 | IBM EBCDIC - Finland/Sweden (20278 + Euro symbol) |
1144 | IBM EBCDIC - Italy (20280 + Euro symbol) |
1145 | IBM EBCDIC - Latin America/Spain (20284 + Euro symbol) |
1146 | IBM EBCDIC - United Kingdom (20285 + Euro symbol) |
1147 | IBM EBCDIC - France (20297 + Euro symbol) |
1148 | IBM EBCDIC - International (500 + Euro symbol) |
1149 | IBM EBCDIC - Icelandic (20871 + Euro symbol) |
1200 | Unicode UCS-2 Little-Endian (BMP of ISO 10646) |
1201 | Unicode UCS-2 Big-Endian |
1250 | ANSI - Central European |
1251 | ANSI - Cyrillic |
1252 | ANSI - Latin I |
1253 | ANSI - Greek |
1254 | ANSI - Turkish |
1255 | ANSI - Hebrew |
1256 | ANSI - Arabic |
1257 | ANSI - Baltic |
1258 | ANSI/OEM - Vietnamese |
1361 | Korean (Johab) |
10000 | MAC - Roman |
10001 | MAC - Japanese |
10002 | MAC - Traditional Chinese (Big5) |
10003 | MAC - Korean |
10004 | MAC - Arabic |
10005 | MAC - Hebrew |
10006 | MAC - Greek I |
10007 | MAC - Cyrillic |
10008 | MAC - Simplified Chinese (GB 2312) |
10010 | MAC - Romania |
10017 | MAC - Ukraine |
10021 | MAC - Thai |
10029 | MAC - Latin II |
10079 | MAC - Icelandic |
10081 | MAC - Turkish |
10082 | MAC - Croatia |
12000 | Unicode UCS-4 Little-Endian |
12001 | Unicode UCS-4 Big-Endian |
20000 | CNS - Taiwan |
20001 | TCA - Taiwan |
20002 | Eten - Taiwan |
20003 | IBM5550 - Taiwan |
20004 | TeleText - Taiwan |
20005 | Wang - Taiwan |
20105 | IA5 IRV International Alphabet No. 5 (7-bit) |
20106 | IA5 German (7-bit) |
20107 | IA5 Swedish (7-bit) |
20108 | IA5 Norwegian (7-bit) |
20127 | US-ASCII (7-bit) |
20261 | T.61 |
20269 | ISO 6937 Non-Spacing Accent |
20273 | IBM EBCDIC - Germany |
20277 | IBM EBCDIC - Denmark/Norway |
20278 | IBM EBCDIC - Finland/Sweden |
20280 | IBM EBCDIC - Italy |
20284 | IBM EBCDIC - Latin America/Spain |
20285 | IBM EBCDIC - United Kingdom |
20290 | IBM EBCDIC - Japanese Katakana Extended |
20297 | IBM EBCDIC - France |
20420 | IBM EBCDIC - Arabic |
20423 | IBM EBCDIC - Greek |
20424 | IBM EBCDIC - Hebrew |
20833 | IBM EBCDIC - Korean Extended |
20838 | IBM EBCDIC - Thai |
20866 | Russian - KOI8-R |
20871 | IBM EBCDIC - Icelandic |
20880 | IBM EBCDIC - Cyrillic (Russian) |
20905 | IBM EBCDIC - Turkish |
20924 | IBM EBCDIC - Latin-1/Open System (1047 + Euro symbol) |
20932 | JIS X 0208-1990 & 0121-1990 |
20936 | Simplified Chinese (GB2312) |
21025 | IBM EBCDIC - Cyrillic (Serbian, Bulgarian) |
21027 | Extended Alpha Lowercase |
21866 | Ukrainian (KOI8-U) |
28591 | ISO 8859-1 Latin I |
28592 | ISO 8859-2 Central Europe |
28593 | ISO 8859-3 Latin 3 |
28594 | ISO 8859-4 Baltic |
28595 | ISO 8859-5 Cyrillic |
28596 | ISO 8859-6 Arabic |
28597 | ISO 8859-7 Greek |
28598 | ISO 8859-8 Hebrew |
28599 | ISO 8859-9 Latin 5 |
28605 | ISO 8859-15 Latin 9 |
29001 | Europa 3 |
38598 | ISO 8859-8 Hebrew |
50220 | ISO 2022 Japanese with no halfwidth Katakana |
50221 | ISO 2022 Japanese with halfwidth Katakana |
50222 | ISO 2022 Japanese JIS X 0201-1989 |
50225 | ISO 2022 Korean |
50227 | ISO 2022 Simplified Chinese |
50229 | ISO 2022 Traditional Chinese |
50930 | Japanese (Katakana) Extended |
50931 | US/Canada and Japanese |
50933 | Korean Extended and Korean |
50935 | Simplified Chinese Extended and Simplified Chinese |
50936 | Simplified Chinese |
50937 | US/Canada and Traditional Chinese |
50939 | Japanese (Latin) Extended and Japanese |
51932 | EUC - Japanese |
51936 | EUC - Simplified Chinese |
51949 | EUC - Korean |
51950 | EUC - Traditional Chinese |
52936 | HZ-GB2312 Simplified Chinese |
54936 | Windows XP: GB18030 Simplified Chinese (4 Byte) |
57002 | ISCII Devanagari |
57003 | ISCII Bengali |
57004 | ISCII Tamil |
57005 | ISCII Telugu |
57006 | ISCII Assamese |
57007 | ISCII Oriya |
57008 | ISCII Kannada |
57009 | ISCII Malayalam |
57010 | ISCII Gujarati |
57011 | ISCII Punjabi |
65000 | Unicode UTF-7 |
65001 | Unicode UTF-8 |
Identifier | Name |
1 | ASCII |
2 | NEXTSTEP |
3 | JapaneseEUC |
4 | UTF8 |
5 | ISOLatin1 |
6 | Symbol |
7 | NonLossyASCII |
8 | ShiftJIS |
9 | ISOLatin2 |
10 | Unicode |
11 | WindowsCP1251 |
12 | WindowsCP1252 |
13 | WindowsCP1253 |
14 | WindowsCP1254 |
15 | WindowsCP1250 |
21 | ISO2022JP |
30 | MacOSRoman |
10 | UTF16String |
0x90000100 | UTF16BigEndian |
0x94000100 | UTF16LittleEndian |
0x8c000100 | UTF32String |
0x98000100 | UTF32BigEndian |
0x9c000100 | UTF32LittleEndian |
65536 | Proprietary |
- 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.
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.
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 (PHTMLMailer Component)
HTMLMailer Errors
169 Invalid image index (out of range). | |
170 Invalid attachment index (out of range). |
The component may also return one of the following error codes, which are inherited from other components.
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. |
SMTP Errors
118 Firewall Error. Error message contains detailed description. | |
161 SMTP protocol error. Description contains the server reply. | |
162 Error communicating with server. Error text is attached. | |
163 Please specify a MailServer. | |
164 Please specify a sender (From). | |
165 Please specify a recipient. | |
166 Busy executing current method. | |
301 Operation interrupted. | |
302 Can't open AttachedFile. |
The component may also return one of the following error codes, which are inherited from other components.
TCPClient Errors
100 You cannot change the RemotePort at this time. A connection is in progress. | |
101 You cannot change the RemoteHost (Server) at this time. A connection is in progress. | |
102 The RemoteHost address is invalid (0.0.0.0). | |
104 Already connected. If you want to reconnect, close the current connection first. | |
106 You cannot change the LocalPort at this time. A connection is in progress. | |
107 You cannot change the LocalHost at this time. A connection is in progress. | |
112 You cannot change MaxLineLength at this time. A connection is in progress. | |
116 RemotePort cannot be zero. Please specify a valid service port number. | |
117 You cannot change the UseConnection option while the component is active. | |
135 Operation would block. | |
201 Timeout. | |
211 Action impossible in control's present state. | |
212 Action impossible while not connected. | |
213 Action impossible while listening. | |
301 Timeout. | |
302 Could not open file. | |
434 Unable to convert string to selected CodePage. | |
1105 Already connecting. If you want to reconnect, close the current connection first. | |
1117 You need to connect first. | |
1119 You cannot change the LocalHost at this time. A connection is in progress. | |
1120 Connection dropped by remote host. |
SSL Errors
270 Cannot load specified security library. | |
271 Cannot open certificate store. | |
272 Cannot find specified certificate. | |
273 Cannot acquire security credentials. | |
274 Cannot find certificate chain. | |
275 Cannot verify certificate chain. | |
276 Error during handshake. | |
280 Error verifying certificate. | |
281 Could not find client certificate. | |
282 Could not find server certificate. | |
283 Error encrypting data. | |
284 Error decrypting data. |
TCP/IP Errors
10004 [10004] Interrupted system call. | |
10009 [10009] Bad file number. | |
10013 [10013] Access denied. | |
10014 [10014] Bad address. | |
10022 [10022] Invalid argument. | |
10024 [10024] Too many open files. | |
10035 [10035] Operation would block. | |
10036 [10036] Operation now in progress. | |
10037 [10037] Operation already in progress. | |
10038 [10038] Socket operation on non-socket. | |
10039 [10039] Destination address required. | |
10040 [10040] Message too long. | |
10041 [10041] Protocol wrong type for socket. | |
10042 [10042] Bad protocol option. | |
10043 [10043] Protocol not supported. | |
10044 [10044] Socket type not supported. | |
10045 [10045] Operation not supported on socket. | |
10046 [10046] Protocol family not supported. | |
10047 [10047] Address family not supported by protocol family. | |
10048 [10048] Address already in use. | |
10049 [10049] Can't assign requested address. | |
10050 [10050] Network is down. | |
10051 [10051] Network is unreachable. | |
10052 [10052] Net dropped connection or reset. | |
10053 [10053] Software caused connection abort. | |
10054 [10054] Connection reset by peer. | |
10055 [10055] No buffer space available. | |
10056 [10056] Socket is already connected. | |
10057 [10057] Socket is not connected. | |
10058 [10058] Can't send after socket shutdown. | |
10059 [10059] Too many references, can't splice. | |
10060 [10060] Connection timed out. | |
10061 [10061] Connection refused. | |
10062 [10062] Too many levels of symbolic links. | |
10063 [10063] File name too long. | |
10064 [10064] Host is down. | |
10065 [10065] No route to host. | |
10066 [10066] Directory not empty | |
10067 [10067] Too many processes. | |
10068 [10068] Too many users. | |
10069 [10069] Disc Quota Exceeded. | |
10070 [10070] Stale NFS file handle. | |
10071 [10071] Too many levels of remote in path. | |
10091 [10091] Network subsystem is unavailable. | |
10092 [10092] WINSOCK DLL Version out of range. | |
10093 [10093] Winsock not loaded yet. | |
11001 [11001] Host not found. | |
11002 [11002] Non-authoritative 'Host not found' (try again or check DNS setup). | |
11003 [11003] Non-recoverable errors: FORMERR, REFUSED, NOTIMP. | |
11004 [11004] Valid name, no data record (check DNS setup). |
OpenPGP Errors
101 Cannot decode ASCII Armor data. | |
102 Unknown ASCII Armor data type. | |
103 Checksum failed. | |
104 Unknown ASCII Armor header. | |
105 Cannot decode PGP packet. | |
106 Cannot encode PGP packet. | |
107 Unknown PGP packet tag. | |
108 Unsupported version. | |
109 Unsupported algorithm. | |
110 Unknown subpacket. | |
111 Internal error. | |
112 Feature not supported. | |
113 Secret data was not encrypted. | |
114 Cannot find the key. | |
115 Error reading file. | |
116 Error writing file. | |
117 Error reading key. | |
118 Error writing key. | |
119 Cannot verify signature. | |
120 Cannot create signature. | |
121 Invalid UserId. | |
122 Invalid passphrase. | |
123 Data encryption failed. | |
124 Error creating key. | |
125 Unsupported symmetric algorithm. | |
126 Unsupported hash. | |
127 Unsupported compression algorithm. | |
128 Invalid key usage. | |
129 Component is busy. | |
130 Error decrypting data. | |
131 Data is not compressed. | |
132 Error decompressing data. | |
133 Error compressing data. | |
134 Unsupported signature. | |
135 Failed to overwrite file. | |
141 No input. | |
142 Signing was required, but the message was not signed. | |
143 Encryption was required, but the message was not encrypted. | |
146 No data integrity packet was found (MDC), but one was required. | |
200 Out of memory. |