MailMan

Set this property to 1 to request that the currently running operation be aborted.

This applies to methods that may take time to complete, such as methods that perform network communication or lengthy file operations. Methods that always complete quickly are generally not affected.

If no method is currently running, the property is automatically reset to 0 when the next method call begins. When an abort actually occurs, Chilkat resets this property to 0.

Both synchronous and asynchronous method calls can be aborted. A synchronous method can be aborted by setting this property from another thread.

Controls whether an email should be sent when one or more recipients are rejected by the SMTP server.

The default value is 0, which means Chilkat continues sending even if some recipients are rejected.

When set to 1, the email is not sent to any recipients if the SMTP server rejects any recipient address.

Important: This property only works when SMTP pipelining is disabled. Because SmtpPipelining is 1 by default, set SmtpPipelining = 0 when all-or-none behavior is required.

Note: SMTP servers do not always verify recipient addresses. Even when they do, the server can usually verify only addresses within domains it controls.

When 1, Chilkat automatically adjusts common SMTP and POP3 SSL/TLS settings based on the configured port numbers.

• If SmtpPort = 465, Chilkat sets StartTLS = 0 and SmtpSsl = 1.
• If SmtpPort = 25, Chilkat sets SmtpSsl = 0.
• If MailPort = 995, Chilkat sets PopSsl = 1.
• If MailPort = 110, Chilkat sets PopSsl = 0.

The default value is 1.

Controls whether Chilkat automatically generates a unique Message-ID header when an email is sent.

The default behavior is to generate a new unique Message-ID at send time. This allows the same Email object to be reused without accidentally sending duplicate message IDs.

If duplicate message IDs are used, some SMTP servers may treat the message as a duplicate and discard it.

When automatic generation is enabled, calling GetHeaderField("Message-ID") before sending will not necessarily show the actual message ID that Chilkat sends.

Set this property to 0 to prevent Chilkat from automatically generating the Message-ID header.

When 1, Chilkat automatically sends the SMTP RSET command before sending a new email over an already-open SMTP connection.

This helps ensure the SMTP session is in a clean state before the next email is sent.

The default value is 0.

Note: This property only applies when reusing an existing SMTP connection.

Controls whether Chilkat automatically unwraps digitally signed or encrypted email when the message is downloaded or loaded from MIME.

The default value is 1. When enabled, Chilkat verifies signatures and decrypts encrypted content when possible. The results are made available through the email object's security-related properties and methods.

Set this property to 0 if you want signed or encrypted attachments, such as .p7m or .p7s files, to remain as ordinary attachments.

Important: Signature verification and decryption must occur when the original MIME is first loaded. After MIME is parsed into Chilkat's internal email object format, the exact original MIME bytes are no longer available, and the signature can no longer be verified.

Specifies the local IP address to use when connecting from a computer that has multiple network interfaces or multiple IP addresses.

For most computers, this property should be left unset. Chilkat will automatically use the default local IP address.

The value should be a numeric IP address, such as 165.164.55.124, not a hostname.

Contains a numeric code describing the result of the last connection attempt. This applies to the last connection made, or attempted, by any method.

The maximum number of seconds to wait while attempting to connect to an SMTP or POP3 server.

The default value is 30 seconds.

If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.

Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.

Possible causes of hangs include:

• A timeout property set to 0, indicating an infinite timeout.
• A hang occurring within an event callback in the application code.
• An internal bug in the Chilkat code causing the hang.

The DsnEnvid property specifies the SMTP DSN ENVID value, which is an arbitrary identifier attached to the SMTP envelope. The same value is typically returned in DSN responses so the sending application can correlate delivery notifications with the original outbound email.

Common choices for DsnEnvid include:

• An internal message ID:

  MSG-10004521

• A GUID or UUID:

  550e8400-e29b-41d4-a716-446655440000

• An order or transaction number:

  ORDER-847291

• A timestamp-based identifier:

  MAIL-20260515-153045-001

• A composite identifier combining application, customer, and message IDs:

  billing|cust-9182|invoice-44381

The value should uniquely identify the outbound email within your application. It does not need to match the MIME Message-ID header, although some applications choose to use the same identifier for both.

About SMTP DSN

SMTP DSN means Delivery Status Notification. It is an optional SMTP service extension defined by RFC 3461 that allows the sender to request delivery-status reports from the SMTP server.

DSN allows an application to request notifications such as:

• Successful delivery
• Delivery failure
• Delayed delivery

It also allows the sender to specify whether the returned notification should include the full original message or only the message headers.

In Chilkat.MailMan, DSN behavior is controlled using:

• DsnEnvid — sets the SMTP ENVID envelope identifier.
• DsnNotify — controls when notifications are requested, such as SUCCESS, FAILURE, DELAY, or NEVER.
• DsnRet — controls whether DSN responses include the full message or only headers.

DSN is an optional SMTP extension and is not supported by all SMTP servers. A server supports DSN only if it advertises the DSN capability in response to the SMTP EHLO command.

The IsSmtpDsnCapable method can be used to determine whether the SMTP server supports DSN.

Even when DSN is supported, some SMTP servers or downstream mail systems may ignore or partially honor DSN requests.

Specifies the SMTP DSN NOTIFY parameter used when sending email.

The value may be left empty, set to NEVER, or set to a comma-separated combination of SUCCESS, FAILURE, and DELAY.

Specifies the SMTP DSN RET parameter used when sending email.

The value may be left empty, set to FULL to request the full message in DSN notifications, or set to HDRS to request only the message headers.

When 1, Chilkat embeds the signing certificate chain in signed email.

Certificates are included up to, but not including, the root certificate. If IncludeRootCert is also 1, the root CA certificate is included as well.

The default value is 0

Enables automatic resolution of passwords and credentials from secure local storage.

When set to 1, supported properties and methods can accept a Chilkat secret specification string instead of a literal password. Secret specification strings begin with !!.

Chilkat resolves secrets from:

• Windows Credential Manager on Windows.
• Apple Keychain on macOS.

The secret specification format is: !![appName|]service[|domain]|username

This applies to PopPassword, SmtpPassword, HttpProxyPassword, SocksPassword, PopPasswordBase64, and SshAuthenticatePw.

The default value is 0.

Specifies a filter expression applied by methods such as LoadXmlFile, LoadXmlString, LoadMbx, CopyMail, and TransferMail.

When a filter is present, only emails matching the expression are returned. For TransferMail, only matching emails are removed from the mail server.

Example expressions:

Body like "mortgage rates*"
Subject contains "update" and From contains "chilkat"
To = "info@chilkatsoft.com"

Rules for filter expressions:

• Any MIME header field name may be used. Header names are case-insensitive.
• Literal strings are enclosed in double quotes.
• String matching is case-insensitive.
• The * wildcard matches zero or more characters.
• Parentheses may be used to control precedence.
• Logical operators are AND, OR, and NOT.
• String comparison operators include CONTAINS and LIKE.

Note: Filtering works on text strings only, not dates or numbers.

Specifies the interval, in milliseconds, between AbortCheck event callbacks.

This allows an application to periodically decide whether a long-running operation should be aborted.

The default value is 0, which means no AbortCheck callbacks are generated.

Specifies the hostname sent in the SMTP EHLO or HELO command.

The default value is an empty string, which causes Chilkat to use the local computer's hostname.

HttpProxyAuthMethod

Specifies the authentication method used when connecting through an HTTP proxy that requires authentication.

Valid values are Basic and NTLM.

Specifies the optional NTLM domain when using NTLM authentication with an HTTP proxy.

Specifies the hostname or IPv4 address of the HTTP proxy to use.

Specifies the password used when authenticating to an HTTP proxy.

Specifies the port number of the HTTP proxy.

Common HTTP proxy ports include 8080 and 3128.

Specifies the username used when authenticating to an HTTP proxy.

Controls whether POP3 deletions are finalized immediately.

The default value is 1. When enabled, any method that deletes email from the POP3 server also sends a QUIT command and closes the POP3 session so the deletion is committed immediately.

In POP3, the DELE command only marks a message for deletion. The message is not actually deleted until the session ends with QUIT.

If ImmediateDelete is set to 0, your application must call Pop3EndSession to finalize the deletions.

Controls whether the root CA certificate is included in the S/MIME signature of a signed email.

This property only applies when EmbedCertChain is 1.

Returns 1 if Chilkat believes the POP3 connection is still open.

Accessing this property does not send any command to the POP3 server. If the server has disconnected but Chilkat has not yet attempted further communication, this property may still return 1.

To verify that the POP3 connection is actually alive, call Pop3Noop.

Returns 1 if Chilkat believes the SMTP connection is still open.

Accessing this property does not communicate with the SMTP server. A lost connection may not be detected until the next SMTP command is sent.

To verify that the SMTP connection is actually alive, call SmtpNoop.

This property is mainly used in SQL Server stored procedures to retrieve binary data from the last method call that returned binary data. It is only accessible if Chilkat.Global.KeepBinaryResult is set to 1. This feature allows for the retrieval of large varbinary results in an SQL Server environment, which has restrictions on returning large data via method calls, though temp tables can handle binary properties.

Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.

Indicates the success or failure of the most recent method call: 1 means success, 0 means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.

Contains the last SMTP status code returned by the SMTP server during the most recent SMTP operation.

SMTP status codes are numeric reply codes defined by the SMTP protocol. They indicate the result of SMTP protocol commands such as EHLO, AUTH, MAIL FROM, RCPT TO, and DATA.

In general:

• 2xx — Success. The requested action completed successfully.
• 3xx — Intermediate success. Additional information or authentication data is required.
• 4xx — Temporary failure. The operation failed, but retrying later may succeed.
• 5xx — Permanent failure. The request was rejected and retrying will usually not help unless something changes.

Contains the text message associated with the last SMTP status code received from the server.

In SQL Server stored procedures, this property holds the string return value of the most recent method call that returns a string. It is accessible only when Chilkat.Global.KeepStringResult is set to TRUE. SQL Server has limitations on string lengths returned from methods and properties, but temp tables can be used to access large strings.

The length, in characters, of the string contained in the LastStringResult property.

Specifies a local file path where Chilkat writes each message exactly as it was received from the POP3 server.

This is useful for debugging problems involving MIME structure, encodings, attachments, or server behavior.

Specifies a local file path where Chilkat writes the exact MIME message sent to the SMTP server.

This is useful for inspecting the final MIME produced by Chilkat.

Specifies the POP3 server hostname or IP address.

Do not include http:// or https://. The value should be a hostname such as pop.example.com or an IPv4/IPv6 address.

Specifies the POP3 server port number.

The default value is 110.

The standard POP3 ports and their associated Chilkat.MailMan property settings are described below.

mailman.MailPort = 995;
mailman.PopSsl = true;

mailman.MailPort = 110;
mailman.PopSsl = false;
mailman.Pop3Stls = false;
mailman.Pop3StlsIfPossible = false;

mailman.MailPort = 110;
mailman.PopSsl = false;
mailman.Pop3Stls = true;

mailman.MailPort = 110;
mailman.PopSsl = false;
mailman.Pop3StlsIfPossible = true;

Important: PopSsl and Pop3Stls represent two different approaches to TLS security:

• PopSsl = true means the connection begins as SSL/TLS from the very start (implicit TLS).
• Pop3Stls = true means the connection begins unencrypted and is later upgraded to TLS using the POP3 STLS command (explicit TLS).

These two approaches are mutually exclusive and should not both be enabled at the same time.

Modern POP3 servers most commonly use either:

• 995 with PopSsl = true, or
• 110 with Pop3Stls = true.

Limits the number of messages Chilkat attempts to retrieve from the POP3 server in a single method call.

This is useful for large mailboxes. For example, setting MaxCount = 100 allows an application to download messages in batches of 100.

Specifies the OAuth2 access token to be used for POP3 or SMTP XOAUTH2 authentication.

When this property is set, Chilkat will use the SMTP or POP3 AUTH XOAUTH2 authentication mechanism if supported by the server.

For POP3 XOAUTH2 authentication:

• PopPassword should be left empty, or explicitly set to the empty string.
• SmtpPassword should be left unset, or set to the empty string.

The OAuth2 access token is sent as a bearer token during the AUTH XOAUTH2 authentication exchange.

Controls the MIME format used for digitally signed email.

When set to 0, Chilkat creates a multipart/signed email. In this format, the original email content remains visible as a normal MIME body part, and the digital signature is included as a separate MIME part.

The top-level MIME Content-Type header will look similar to:

Content-Type: multipart/signed;
    protocol="application/pkcs7-signature";
    micalg=sha-256;
    boundary="------------040808030405050402070604"

This is commonly referred to as a detached signature because the signed content exists separately from the signature itself.

When set to 1, Chilkat creates an opaque signed email using PKCS#7 signed-data format. In this case, the original MIME content is encapsulated inside the PKCS#7 signature structure.

The top-level MIME Content-Type header will look similar to:

Content-Type: application/pkcs7-mime;
    smime-type="signed-data";
    name="smime.p7m"; micalg=sha-256

This format is historically known as opaque signing because the original message content is wrapped inside the PKCS#7 signed object and is not directly visible as ordinary MIME body parts.

The default value is 1.

Specifies the filename used in the Content-Disposition header when sending a PKCS#7 encrypted email.

The default value is smime.p7m.

Specifies the filename used in the Content-Disposition header when sending an opaque signed PKCS#7 email.

The default value is smime.p7m.

Specifies the filename used in the Content-Disposition header when sending a signed email with a detached PKCS#7 signature.

The default value is smime.p7s.

This property is only valid in programming environments and languages that allow for event callbacks.

Sets the value that represents 100% completion for PercentDone event callbacks.

The default value is 100, meaning progress values range from 0 to 100. Setting this property to a larger value provides finer granularity. For example, setting PercentDoneScale = 1000 allows progress to be reported in tenths of a percent.

For example, if PercentDoneScale = 1000, then a callback value of 453 represents 45.3% complete.

The value is clamped to a minimum of 10 and a maximum of 100000.

Returns 0 when no POP3 session is active.

Otherwise, returns a positive integer that increments each time a new POP3 session is established. This can be used to detect whether a new session has started.

Contains the accumulated raw POP3 commands sent to the server and the raw responses received from the server.

This property is read-only. To clear it, call ClearPop3SessionLog.

Controls whether SPA, also known as NTLM authentication, is used for POP3.

Set this property to 1 to use SPA authentication. No other programming changes are required.

The default value is 0.

Note: If SPA/NTLM authentication fails, set Global.DefaultNtlmVersion = 1 and retry.

Indicates whether the POP3 server's SSL/TLS certificate was successfully verified during the connection.

This property is meaningful only when connecting via SSL/TLS.

Controls whether Chilkat requires the POP3 connection to be upgraded to TLS using the STLS command.

When set to 1, Chilkat initially connects without encryption, typically on port 110, and then sends STLS to convert the connection to TLS.

Use this only with POP3 servers known to support STLS. When this property is 1, PopSsl should be 0.

The default value is 0.

Controls whether Chilkat uses POP3 STLS automatically when the server supports it.

If the server supports STLS, the connection is upgraded to TLS. If the server does not support STLS, the connection remains unencrypted.

The default value is 0.

Specifies the POP3 password.

On Windows, if Pop3SPA is enabled, both PopUsername and PopPassword may be set to "default" to use the credentials of the current logged-on Windows user.

Provides a way to specify the POP3 password as a Base64-encoded string.

Controls whether implicit SSL/TLS is used when connecting to the POP3 server.

When set to 1, the TLS connection is established immediately when connecting. The POP3 SSL/TLS port is typically 995.

The default value is 0.

Specifies the POP3 login name.

On Windows, if Pop3SPA is enabled, both PopUsername and PopPassword may be set to "default" to use the credentials of the current logged-on Windows user.

Controls whether IPv6 is preferred over IPv4 when both are available for a hostname.

The default value is 0, which means IPv4 is preferred.

Specifies the maximum number of seconds to wait when the SMTP or POP3 server stops responding.

The default value is 30 seconds.

Controls whether Chilkat requires SMTP and POP3 SSL/TLS server certificates to be successfully verified.

When set to 1, Chilkat rejects the connection if the server certificate is expired or if the certificate signature cannot be verified.

The default value is 0.

This property applies only to SSL/TLS connections.

Controls whether the email's Date header is reset to the current date and time when an email is loaded.

This applies to methods such as LoadMbx, LoadEml, LoadMime, LoadXml, and LoadXmlString.

The default value is 0.

Specifies the buffer size used by the underlying TCP/IP socket when sending data.

The default value is 32767.

Controls how email is sent to distribution lists.

When 1, Chilkat sends one email per recipient. Each message has the recipient's address in the To header.

When 0, Chilkat sends messages in batches of up to 100 BCC recipients at a time.

For example, a distribution list with 350 recipients would result in four messages: three with 100 BCC recipients, and one with 50 BCC recipients.

The default value is 1.

Specifies the maximum size, in bytes, of messages Chilkat will retrieve from a POP3 server.

Messages larger than this limit are not downloaded.

The default value is 0, which means no size limit.

Specifies the SMTP authentication method to use.

This property should usually be left empty so Chilkat can automatically choose the most secure method advertised by the SMTP server.

If the server does not advertise authentication methods, or if a specific method must be forced, set this property to one of: NONE, LOGIN, PLAIN, CRAM-MD5, or NTLM.

Note: If NTLM authentication fails, set Global.DefaultNtlmVersion = 1 and retry.

Contains a keyword describing the result or failure reason for the last SMTP operation.

Specifies the SMTP server hostname or IP address.

Do not include http:// or https://. The value may be a hostname, IPv4 address, or IPv6 address.

Specifies the Windows domain to use when logging in to an SMTP server with NTLM authentication.

Leave this property empty if no domain is required.

Specifies the SMTP envelope sender address used in the MAIL FROM command.

This address receives bounce messages and identifies the originator of the SMTP transaction. It may differ from the From MIME header.

If left empty, Chilkat uses the email address from the message's From header.

SMTP servers may reject the envelope sender based on DNS, SPF, or other server policy checks.

Specifies the password used for SMTP authentication.

Chilkat supports SMTP authentication methods such as LOGIN, PLAIN, CRAM-MD5, and NTLM, and normally chooses the most secure available method automatically.

If NTLM authentication is used, SmtpUsername and SmtpPassword may be set to the keyword "default" to use the current Windows logged-on credentials.

Controls whether SMTP pipelining is used when the server advertises support for it.

The default value is 1.

Set this property to 0 to prevent SMTP pipelining. This is required when using AllOrNone.

Specifies the SMTP server port.

The default value is 25. If using implicit SSL/TLS with SmtpSsl = 1, the common port is 465.

Contains the accumulated raw SMTP commands sent to the server and raw responses received from the server.

This property is read-only. To clear it, call ClearSmtpSessionLog.

Controls whether Chilkat uses implicit SSL/TLS when connecting to the SMTP server.

When set to 1, the TLS connection is established immediately when the TCP connection is opened.

Indicates whether the SMTP server's SSL/TLS certificate was successfully verified during the connection.

This property is meaningful only when an SSL/TLS SMTP connection is used.

Specifies the username used for SMTP authentication.

If SmtpAuthMethod is NTLM, SmtpUsername and SmtpPassword may be set to the keyword "default" to use the current Windows logged-on credentials.

Specifies the SOCKS4 or SOCKS5 proxy hostname or IPv4 address.

This property is used only when SocksVersion is set to 4 or 5.

Specifies the SOCKS5 proxy password, if authentication is required.

SOCKS4 does not use passwords, so this property applies only to SOCKS5.

Specifies the SOCKS proxy port.

The default value is 1080. This property applies only when SocksVersion is set to 4 or 5.

Specifies the SOCKS4 or SOCKS5 proxy username.

This property is used only when SocksVersion is set to 4 or 5.

Specifies whether a SOCKS proxy is used.

• 0 — no SOCKS proxy is used. This is the default.
• 4 — connect through a SOCKS4 proxy.
• 5 — connect through a SOCKS5 proxy.

Sets the socket receive buffer size.

The default value is 4194304.

This property should normally be left unchanged. It may be increased if download performance is slow. Values should preferably be multiples of 4096.

Sets the socket send buffer size.

The default value is 262144.

This property should normally be left unchanged. It may be increased if upload performance is slow. Testing values such as 512K or 1MB is reasonable. Values should preferably be multiples of 4096.

Specifies the TLS cipher suites Chilkat is allowed to offer when establishing SSL/TLS connections.

The default value is an empty string, meaning Chilkat may offer all implemented cipher suites. To restrict the allowed ciphers, set this property to a comma-separated list of cipher suite names, ordered by preference.

The cipher suites supported by Chilkat are:

Important: The client offers a list of allowed cipher suites, but the server chooses the final cipher suite from that list.

This property can also include special keywords:

• rsa1024 — reject server certificates with RSA keys smaller than 1024 bits.
• rsa2048 — reject server certificates with RSA keys smaller than 2048 bits.
• secure-renegotiation — require secure renegotiation as defined by RFC 5746.
• best-practices — use Chilkat's current best-practice cipher policy.

The best-practices setting currently requires RSA server keys of at least 1024 bits, requires secure renegotiation, and disallows RC4, DES, and 3DES ciphers.

Example:

TLS_DHE_RSA_WITH_AES_256_CBC_SHA256, TLS_RSA_WITH_AES_256_CBC_SHA, rsa1024, secure-renegotiation

Selects the SSL/TLS protocol version used for secure SMTP and POP3 connections.

Possible values include:

• default
• TLS 1.3
• TLS 1.2
• TLS 1.1
• TLS 1.0
• SSL 3.0
• TLS 1.3 or higher
• TLS 1.2 or higher
• TLS 1.1 or higher
• TLS 1.0 or higher

The default value is default, which allows Chilkat to choose the protocol dynamically based on the server's requirements.

Choosing an exact protocol version can cause the connection to fail unless that exact version is negotiated. In most cases, using an or higher setting is preferable.

Controls whether Chilkat requires SMTP STARTTLS.

When set to 1, Chilkat connects to the SMTP server normally and then sends the STARTTLS command to upgrade the connection to SSL/TLS before authenticating and sending email.

The default value is 0.

This property applies to SMTP only, not POP3.

Controls whether Chilkat uses SMTP STARTTLS automatically when the server supports it.

When set to 1, Chilkat upgrades the SMTP connection to TLS if the server advertises STARTTLS support. If STARTTLS is not supported, the connection remains unencrypted.

The default value is 1.

Use StartTLS = 1 instead when encryption is required and the connection should fail if STARTTLS is unavailable.

This property applies to SMTP only, not POP3.

Contains the current or most recently negotiated TLS cipher suite.

If no TLS connection has been established, or if the TLS connection attempt failed, this property is empty.

Example value:

TLS_DHE_RSA_WITH_AES_256_CBC_SHA256

Specifies the expected SPKI fingerprints for TLS public key pinning.

During the TLS handshake, Chilkat compares the server certificate's public key fingerprint against this pin set. If none of the pins match, the TLS handshake is aborted and the connection fails.

The format is:

hash_algorithm, encoding, SPKI_fingerprint_1, SPKI_fingerprint_2, ...

Example with one SHA-256 Base64 pin:

sha256, base64, lKg1SIqyhPSK19tlPbjl8s02yChsVTDklQpkMCHvsTE=

Example with two SHA-256 Base64 pins:

sha256, base64, 4t37LpnGmrMEAG8HEz9yIrnvJV2euVRwCLb9EH5WZyI=, 68b0G5iqMvWVWvUCjMuhLEyekM5729PadtnU5tdXZKs=

Supported hash algorithms include sha1, sha256, sha384, sha512, md2, md5, haval, ripemd128, ripemd160, ripemd256, and ripemd320.

Supported encodings include base64, hex, and other Chilkat-supported encodings.

Contains the current or most recently negotiated TLS protocol version.

If no TLS connection has been established, or if the TLS connection attempt failed, this property is empty.

Possible values include SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2, and TLS 1.3.

Provides a comma-separated list of uncommon option keywords.

This property defaults to an empty string and should normally remain empty.

• ProtectFromVpn — introduced in v9.5.0.80. On Android, bypasses any installed or active VPN.
• SmtpLoginAnsi — introduced in v9.5.0.97. Causes SMTP login and password strings containing non-ASCII characters to be sent using ANSI encoding instead of UTF-8. This restores the older Chilkat behavior for SMTP servers that expect ANSI credentials.

Controls whether Chilkat automatically uses APOP authentication when the POP3 server supports it.

The default value is 0.

If set to 1, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is 0. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.

Version of the component/library, such as "10.1.0"

Adds a PFX/PKCS#12 certificate store to the MailMan object's internal list of sources used for locating certificates and private keys.

The PFX data is supplied in the bd object, which should contain the bytes of a .pfx or .p12 file.

The added PFX source is searched when Chilkat needs a certificate and private key for operations such as:

• Decrypting S/MIME encrypted email
• Creating digitally signed email

Multiple PFX sources can be added by calling this method once for each PFX.

On Windows, the registry-based Windows certificate stores are automatically searched when locating certificates and private keys. Therefore, if the required certificate and private key are already installed in the Windows certificate store, explicitly adding a PFX source is often unnecessary.

On macOS, the Apple Keychain is also searched automatically. If the required certificate and private key are already available in the Apple Keychain, it is likewise unnecessary to explicitly add a PFX source.

The password argument specifies the password required to open the PFX.

Returns 1 for success, 0 for failure.

Adds a PFX/PKCS#12 certificate store to the MailMan object's internal list of sources used for locating certificates and private keys.

The pfxData argument contains the bytes of a .pfx / .p12 file.

The added PFX source is searched when Chilkat needs a certificate and private key for operations such as:

• Decrypting S/MIME encrypted email
• Creating digitally signed email

Multiple PFX sources can be added by calling this method once for each PFX.

On Windows, the registry-based Windows certificate stores are automatically searched when locating certificates and private keys. Therefore, if the required certificate and private key are already installed in the Windows certificate store, explicitly adding a PFX source is often unnecessary.

On macOS, the Apple Keychain is also searched automatically. If the required certificate and private key are already available in the Apple Keychain, it is likewise unnecessary to explicitly add a PFX source.

The password argument specifies the password required to open the PFX.

Returns 1 for success, 0 for failure.

Adds a PFX/PKCS#12 file to the MailMan object's internal list of sources used for locating certificates and private keys. The pfxFilePath argument is the path to a .pfx or .p12 file.

The added PFX source is searched when Chilkat needs a certificate and private key for operations such as:

• Decrypting S/MIME encrypted email
• Creating digitally signed email

Multiple PFX sources can be added by calling this method once for each PFX.

On Windows, the registry-based Windows certificate stores are automatically searched when locating certificates and private keys. Therefore, if the required certificate and private key are already installed in the Windows certificate store, explicitly adding a PFX source is often unnecessary.

On macOS, the Apple Keychain is also searched automatically. If the required certificate and private key are already available in the Apple Keychain, it is likewise unnecessary to explicitly add a PFX source.

The password argument specifies the password required to open the PFX.

Returns 1 for success, 0 for failure.

Returns the number of emails currently available in the POP3 mailbox. Returns -1 if an error occurs.

If this method fails, use VerifyPopConnection to test basic TCP/IP connectivity to the POP3 server, and VerifyPopLogin to test whether the POP3 login succeeds. The Verify* methods are intended as diagnostic helpers when a POP3 operation returns an error.

Creates an asynchronous task to call the CheckMail method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Clears the MailMan object's in-memory list of bad email addresses.

When an email-sending method is called, email addresses rejected by the SMTP server are cached in the MailMan object. These rejected addresses can be retrieved by calling GetBadEmailAddresses. This method clears that cached list so the object starts with no remembered bad addresses.

Clears the current contents of the Pop3SessionLog property.

Clears the current contents of the SmtpSessionLog property.

Explicitly closes the current SMTP connection. Before closing the socket connection, Chilkat sends the SMTP QUIT command to the server.

Calling this method is optional in most applications. The MailMan object automatically opens an SMTP connection when an email-sending method is called and no connection is already open. The connection is then kept open so subsequent sends can reuse it. For example, if an application calls SendEmail ten times, the first call opens the SMTP connection, and the following calls send over the same connection.

If an SMTP-related property changes, such as the hostname, username, password, port, or SSL/TLS settings, the existing connection is closed and a new connection is established the next time an email-sending method is called.

The SMTP connection is also closed automatically when the MailMan object is destroyed.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the CloseSmtpConnection method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Marks multiple emails on the POP3 server for deletion. Each email in emailBundle that is still present in the POP3 mailbox is marked for deletion.

In POP3, messages marked for deletion are not permanently removed until the session ends with the QUIT command. If the ImmediateDelete property is 1, which is the default, Chilkat sends QUIT and ends the POP3 session automatically so the deletions are completed immediately. If ImmediateDelete is 0, call Pop3EndSession when finished to send QUIT and finalize the deletions.

When making multiple calls to Delete* methods, it is usually better to set ImmediateDelete to 0, perform all deletion markings, and then call Pop3EndSession once.

Any method that requires communication with the POP3 server will automatically re-establish a session using the current property settings if a session is not already open.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the DeleteBundle method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Marks an email for deletion by its POP3 message number.

Important: Message numbers are specific to a single POP3 session and can change from one session to the next. For example, if a mailbox contains ten messages, they are numbered 1 through 10. If message 1 is deleted and a new POP3 session is opened, the remaining messages are renumbered 1 through 9.

A POP3 session must already be established before this method is called, either explicitly by calling Pop3BeginSession or implicitly by calling another method that opens the session. This method does not automatically begin a new session because doing so could change the message numbers and cause the application to delete a different message than intended.

This method only marks the message for deletion. The message is not removed from the POP3 mailbox until the session is ended by calling Pop3EndSession, which sends the QUIT command.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the DeleteByMsgnum method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Marks an email on the POP3 server for deletion using its UIDL. UIDLs are generally preferred over POP3 message numbers because UIDLs remain stable across sessions for as long as the message remains in the mailbox.

In POP3, messages marked for deletion are not permanently removed until the session ends with the QUIT command. If the ImmediateDelete property is 1, which is the default, Chilkat sends QUIT and ends the POP3 session automatically so the deletion is completed immediately. If ImmediateDelete is 0, call Pop3EndSession when finished to send QUIT and finalize the deletion.

When making multiple calls to Delete* methods, it is usually better to set ImmediateDelete to 0, perform all deletion markings, and then call Pop3EndSession once.

Any method that requires communication with the POP3 server will automatically re-establish a session using the current property settings if a session is not already open.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the DeleteByUidl method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Marks the specified email for deletion on the POP3 server. The email object should represent a message that was retrieved from the same POP3 mailbox and can be matched to a message still present on the server.

In POP3, messages marked for deletion are not permanently removed until the session ends with the QUIT command. If the ImmediateDelete property is 1, which is the default, Chilkat sends QUIT and ends the POP3 session automatically so the deletion is completed immediately. If ImmediateDelete is 0, call Pop3EndSession when finished to send QUIT and finalize the deletion.

When making multiple calls to Delete* methods, it is usually better to set ImmediateDelete to 0, perform all deletion markings, and then call Pop3EndSession once.

Any method that requires communication with the POP3 server will automatically re-establish a session using the current property settings if a session is not already open.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the DeleteEmail method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Marks multiple emails on the POP3 server for deletion. Each message whose UIDL matches an entry in stUidls is marked for deletion.

In POP3, messages marked for deletion are not permanently removed until the session ends with the QUIT command. If the ImmediateDelete property is 1, which is the default, Chilkat sends QUIT and ends the POP3 session automatically so the deletions are completed immediately. If ImmediateDelete is 0, call Pop3EndSession when finished to send QUIT and finalize the deletions.

When making multiple calls to Delete* methods, it is usually better to set ImmediateDelete to 0, perform all deletion markings, and then call Pop3EndSession once.

Any method that requires communication with the POP3 server will automatically re-establish a session using the current property settings if a session is not already open.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the DeleteUidlSet method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Retrieves all emails from the POP3 mailbox and stores them in bundle.

If headersOnly is 1, Chilkat downloads only the message headers and the first numBodyLines lines of the message body. Attachments are not downloaded. If headersOnly is 0, Chilkat downloads the complete messages, including attachments.

If keepOnServer is 1, the downloaded emails remain on the POP3 server. If keepOnServer is 0, the messages may be deleted from the server after full download, depending on the POP3 deletion/session behavior.

Note: keepOnServer applies only when downloading full emails. Header-only downloads do not delete messages from the server, regardless of the value of keepOnServer.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the FetchAll method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Retrieves an email from the POP3 server by UIDL and stores it in email. The message is not deleted from the server.

If headerOnly is 1, Chilkat downloads only the message headers and the first numBodyLines lines of the message body. Attachments are not downloaded. If headerOnly is 0, Chilkat downloads the complete message, including attachments.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the FetchByUidl method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

If a partial email (header-only) was retrieved, this method will download and return the full email from the server using the partial email as an argument.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the FetchFull method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Fetches an email by UIDL and returns the MIME source of the email in a byte array.

Returns a zero-length byte array (as a Variant) on failure.
An empty array will have a UBound of -1 meaning 0 elements.

Creates an asynchronous task to call the FetchMime method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Fetches an email by UIDL and returns the MIME source of the email in uidl.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the FetchMimeBd method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Retrieves an email by its message number and returns the MIME bytes. Note: Message numbers are unique to each POP3 session. For instance, if there are 10 messages in the maildrop, they will be numbered 1 through 10. If message 1 is deleted and a new POP3 session is started, the remaining messages will be renumbered from 1 to 9. Please note that a POP3 connection must be established beforehand. This can be done by explicitly calling Pop3BeginSession or through other methods that implicitly start the session. This method does not initiate a POP3 session automatically.

Returns a zero-length byte array (as a Variant) on failure.
An empty array will have a UBound of -1 meaning 0 elements.

Creates an asynchronous task to call the FetchMimeByMsgnum method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Retrieves an email by its message number and provides the MIME source in bd. Note: Message numbers are unique to each POP3 session. For instance, if there are 10 messages in the maildrop, they will be numbered 1 through 10. If message 1 is deleted and a new POP3 session is started, the remaining messages will be renumbered from 1 to 9. Please note that a POP3 connection must be established beforehand. This can be done by explicitly calling Pop3BeginSession or through other methods that implicitly start the session. This method does not initiate a POP3 session automatically.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the FetchMimeByMsgnumBd method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Retrieves a complete message or header by its message number and stores it in msgNum. The first email has a message number of 1. Messages fetched by this method remain on the server.

Note: Message numbers are unique to each POP3 session.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the FetchOne method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Retrieves a specified range of emails from the POP3 server. If keepOnServer is 1, the emails remain on the server. If headersOnly is 1, only the headers and the first numBodyLines lines of each email are downloaded, without attachments. Otherwise, the entire emails, including attachments, are downloaded. The range of emails to download is determined by startIndex and endIndex. The GetMailboxCount method returns the total number of emails in the POP3 mailbox, with the first email at index 0. The downloaded emails are stored in bundle.

Note: keepOnServer only applies when downloading full emails (not headers-only). Downloading headers-only will not cause the email to be deleted from the server, regardless of keepOnServer.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the FetchRange method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Returns the UIDLs of the emails currently stored on the POP3 server.

POP3 UIDLs (Unique ID Listings) are persistent, unique identifiers assigned by a mail server to each email message in a mailbox. Unlike message numbers, which can change between sessions, UIDLs remain consistent as long as the message exists, allowing email clients to track which messages have already been downloaded—even across multiple sessions—without re-fetching the same emails.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the FetchUidls method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Fetches the email headers or full emails from the POP3 server whose UIDL is present in the uidls. If headersOnly is 1, only the headers and the first numBodyLines lines of each email are downloaded, excluding attachments. Otherwise, the entire emails with attachments are downloaded. The emails are stored in bundle. The downloaded emails are not deleted from the server.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the FetchUidlSet method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Provides information about what transpired in the last method called on this object instance. For many methods, there is no information. However, for some methods, details about what occurred can be obtained by getting the LastJsonData right after the method call returns.

Returns the number of emails on the POP3 server, or -1 for failure.

This method is identical to CheckEmail. It was added for clarity.

Creates an asynchronous task to call the GetMailboxCount method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Returns an XML document with information about the emails in a POP3 mailbox. The XML contains the UIDL and size (in bytes) of each email in the mailbox.

Returns Nothing on failure

Creates an asynchronous task to call the GetMailboxInfoXml method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Returns the total combined size in bytes of all the emails in the POP3 mailbox. This is also known as the mail drop size. Returns -1 on failure.

Creates an asynchronous task to call the GetMailboxSize method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

If the current connection is SSL/TLS, this method returns the digital certificate of the SMTP or POP3 server specified by useSmtp. The certificate is returned in cert.

Returns 1 for success, 0 for failure.

Returns the size of an email (including attachments) given the UIDL of the email on the POP3 server. Returns -1 for failure.

Creates an asynchronous task to call the GetSizeByUidl method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Contacts the SMTP server and determines if it supports the DSN (Delivery Status Notification) features specified by RFC 3461 and supported by the DsnEnvid, DsnNotify, and DsnRet properties. Returns 1 if the SMTP server supports DSN, otherwise returns 0.

Creates an asynchronous task to call the IsSmtpDsnCapable method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Loads a .mbx file containing emails and returns in bundle. If a Filter is present, only emails that match the filter are returned.

Returns 1 for success, 0 for failure.

Loads the caller of the task's async method.

Returns 1 for success, 0 for failure.

Explicitly opens a connection to the SMTP server and authenticates (if a username/password was specified). Calling this method is optional because the SendEmail method and other mail-sending methods will automatically open the connection to the SMTP server if one is not already established.

Note: This method is the equivalent of calling SmtpConnect followed by SmtpAuthenticate.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the OpenSmtpConnection method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Authenticates with the POP3 server using the property settings such as PopUsername, PopPassword, etc. This method should only be called after a successful call to Pop3Connect.

Note 1: The Pop3BeginSession method both connects and authenticates. It is the equivalent of calling Pop3Connect followed by Pop3Authenticate.

Note 2: All methods that communicate with the POP3 server, such as FetchEmail, will automatically connect and authenticate if not already connected and authenticated.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the Pop3Authenticate method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Call to explicitly begin a POP3 session. It is not necessary to call this method because any method requiring an established POP3 session will automatically connect and login if a session is not already open.

Important: All TCP-based Internet communications, regardless of the protocol (such as HTTP, FTP, SSH, IMAP, POP3, SMTP, etc.), and regardless of SSL/TLS, begin with establishing a TCP connection to a remote host:port. External security-related infrastructure such as software firewalls (Windows Firewall), hardware firewalls, anti-virus, at either source or destination (or both) can block the connection. If the connection fails, make sure to check all potential external causes of blockage.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the Pop3BeginSession method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Explicitly establishes a connection to the POP3 server, which includes establishing a secure TLS channel if required, and receives the initial greeting. This method stops short of authenticating. The Pop3Authenticate method should be called after a successful call to this method.

When finished transacting with a POP3 mail server you can disconnect by calling Pop3EndSession or Pop3EndSessionNoQuit.

Note 1: The Pop3BeginSession method both connects and authenticates. It is the equivalent of calling Pop3Connect followed by Pop3Authenticate.

Note 2: All methods that communicate with the POP3 server, such as FetchEmail, will automatically connect and authenticate if not already connected and authenticated.

Important: All TCP-based Internet communications, regardless of the protocol (such as HTTP, FTP, SSH, IMAP, POP3, SMTP, etc.), and regardless of SSL/TLS, begin with establishing a TCP connection to a remote host:port. External security-related infrastructure such as software firewalls (Windows Firewall), hardware firewalls, anti-virus, at either source or destination (or both) can block the connection. If the connection fails, make sure to check all potential external causes of blockage.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the Pop3Connect method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Call to explicitly end a POP3 session (sends the QUIT command and then closes the connection with the POP3 server). If the ImmediateDelete property is set to 0, and emails marked for deletion will be deleted at this time.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the Pop3EndSession method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is identical to Pop3EndSession, but no QUIT command is sent. The client simply disconnects from the POP3 server.

This method should always return 1.

Creates an asynchronous task to call the Pop3EndSessionNoQuit method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Sends a NOOP command to the POP3 server. This may be a useful method to call periodically to keep a connection open, or to verify that the POP3 connection (session) is open and functioning.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the Pop3Noop method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Sends a RSET command to the POP3 server. If any messages have been marked as deleted by the POP3 server, they are unmarked. Calling Pop3Reset resets the POP3 session to a valid, known starting point.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the Pop3Reset method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Sends a raw command to the POP3 server and returns the POP3 server's response. If non-us-ascii characters are included in command, then charset indicates the charset to be used in sending the command (such as utf-8, ansi, iso-8859-1, Shift_JIS, etc.)

Returns Nothing on failure

Creates an asynchronous task to call the Pop3SendRawCommand method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

A quick way to send an email to a single recipient without having to explicitly create an email object.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the QuickSend method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

When you call SendEmail , the email is first processed by rendering it with the specified properties and contents. This may include digital signing, encryption, substituting values for placeholders, and encoding header fields if necessary. The RenderToMime method handles this rendering process without sending the email. The resulting MIME text is what would be sent to the SMTP server if SendEmail were called. Essentially, SendEmail is equivalent to executing RenderToMime followed by SendMime. If successful, the rendered MIME string is returned.

Returns Nothing on failure

The same as RenderToMimeBytes, except the MIME is rendered into renderedMime. The rendered MIME is appended to renderedMime.

Returns 1 for success, 0 for failure.

This method is the same as RenderToMime, but the MIME is returned in a byte array. If an email uses an 8bit or binary MIME encoding, then calling RenderToMime may introduce errors because it is not possible to return non-text binary data as a string. Therefore, calling RenderToMimeBytes is recommended over RenderToMime, unless it is assured that the email (MIME) does not use a binary encoding for non-text data.

Returns a zero-length byte array (as a Variant) on failure.
An empty array will have a UBound of -1 meaning 0 elements.

The same as RenderToMime, except the MIME is rendered into renderedMime. The rendered MIME is appended to renderedMime.

Returns 1 for success, 0 for failure.

Sends a bundle of emails. This is identical to calling SendEmail for each email in the bundle.

If an error occurs when sending one of the emails in the bundle, it will continue with each subsequent email until each email in the bundle has been attempted (unless a fatal error occurs, in which case the send is aborted).

Because it is difficult or impossible to programmatically identify which emails in the bundle failed and which succeeded, it is best to write a loop that sends each email separately (via the SendEmail method).

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SendBundle method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Sends a single email. The connection to the SMTP server will remain open so that a subsequent call to SendEmail (or other email-sending methods) can re-use the same connection. If any properties relating to the SMTP server are changed, such as SmtpHost, SmtpUsername, etc., then the next call to an email-sending method will automatically close the connection and re-establish a connection using the updated property settings.

Important: Some SMTP servers do not actually send the email until the connection is closed. In these cases, it is necessary to call CloseSmtpConnection for the mail to be sent. Most SMTP servers send the email immediately, and it is not required to close the connection.

GMail: If sending via smtp.gmail.com, then send with OAuth2 authentication if possible. Otherwise you will need to change your GMail account settings to allow for sending by less secure apps. See the links below.

Note: After sending email, information about what transpired is available via the LastJsonData method.

Note: Returns 1 if the final SMTP status code in the SMTP session is in the 200's or 300's. See SMTP Server Return Codes

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SendEmail method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Provides complete control over the email that is sent. The MIME text passed in mimeSource (the MIME source of an email) is passed exactly as-is to the SMTP server. The recipients is a comma separated list of recipient email addresses. The fromAddr is the reverse-path email address. This is where bounced email (non-delivery reports) will be delivered. It may be different than the From header field in the mimeSource.

To understand how the fromAddr and recipients relate to the email addresses found in the MIME headers (FROM, TO, CC), see the link below entitled SMTP Protocol in a Nutshell. The fromAddr is what is passed to the SMTP server in the MAIL FROM command. The recipients are the email addresses passed in RCPT TO commands. These are usually the same email addresses found in the MIME headers, but need not be (unless the SMTP server enforces policies that require them to be the same).

Note: Returns 1 if the final SMTP status code in the SMTP session is in the 200's or 300's. See SMTP Server Return Codes

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SendMime method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is the same as SendMimeBytes, except the MIME is passed in an object (mimeData) rather than explicitly passing the bytes.

Note: Returns 1 if the final SMTP status code in the SMTP session is in the 200's or 300's. See SMTP Server Return Codes

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SendMimeBd method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is the same as SendMime, except the MIME is passed in a byte array. This can be important if the MIME uses a binary encoding, or if a DKIM/DomainKey signature is included.

To understand how the fromAddr and recipients relate to the email addresses found in the MIME headers (FROM, TO, CC), see the link below entitled SMTP Protocol in a Nutshell. The fromAddr is what is passed to the SMTP server in the MAIL FROM command. The recipients are the email addresses passed in RCPT TO commands. These are usually the same email addresses found in the MIME headers, but need not be (unless the SMTP server enforces policies that require them to be the same).

Note: Returns 1 if the final SMTP status code in the SMTP session is in the 200's or 300's. See SMTP Server Return Codes

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SendMimeBytes method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Same as SendMime, but the recipient list is read from a text file (distListFilename) containing one email address per line.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SendMimeToList method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Explicitly specifies the certificate to be used for decrypting encrypted email.

Returns 1 for success, 0 for failure.

Explicitly specifies the certificate and associated private key to be used for decrypting S/MIME encrypted email.

Note: In most cases, it is easier to call AddPfxSourceFile or AddPfxSourceData to provide the required cert and private key. On Windows systems where the certificate + private key has already been installed in the default certificate store, nothing needs to be done -- the mailman will automatically locate and use the required cert + private key.

Returns 1 for success, 0 for failure.

Provides a more secure way of setting either the POP3 or SMTP password. The protocol can be pop3 or smtp. When the protocol is pop3, this is equivalent to setting the PopPassword property. When protocol is smtp, this is equivalent to setting the SmtpPassword property.

Returns 1 for success, 0 for failure.

Sets the client-side certificate to be used with SSL connections. This is typically not required, as most SSL connections are such that only the server is authenticated while the client remains unauthenticated.

Returns 1 for success, 0 for failure.

Allows for a client-side certificate to be used for the SSL / TLS connection.

Returns 1 for success, 0 for failure.

Allows for a client-side certificate to be used for the SSL / TLS connection.

Returns 1 for success, 0 for failure.

Authenticates with the SMTP server using the property settings such as SmtpUsername, SmtpPassword, etc. This method should only be called after a successful call to SmtpConnect.

Note 1: The OpenSmtpConnection method both connects and authenticates. It is the equivalent of calling SmtpConnect followed by SmtpAuthenticate.

Note 2: All methods that communicate with the SMTP server, such as SendEmail, will automatically connect and authenticate if not already connected and authenticated.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SmtpAuthenticate method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Explicitly establishes a connection to the SMTP server, which includes establishing a secure TLS channel if required, and receives the initial greeting. This method stops short of authenticating. The SmtpAuthenticate method should be called after a successful call to this method.

Note 1: The OpenSmtpConnection method both connects and authenticates. It is the equivalent of calling SmtpConnect followed by SmtpAuthenticate.

Note 2: All methods that communicate with the SMTP server, such as SendEmail, will automatically connect and authenticate if not already connected and authenticated.

Important: All TCP-based Internet communications, regardless of the protocol (such as HTTP, FTP, SSH, IMAP, POP3, SMTP, etc.), and regardless of SSL/TLS, begin with establishing a TCP connection to a remote host:port. External security-related infrastructure such as software firewalls (Windows Firewall), hardware firewalls, anti-virus, at either source or destination (or both) can block the connection. If the connection fails, make sure to check all potential external causes of blockage.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SmtpConnect method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Sends a no-op to the SMTP server. Calling this method is good for testing to see if the connection to the SMTP server is working and valid. The SmtpNoop method will automatically establish the SMTP connection if it does not already exist.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SmtpNoop method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Returns a list of email addresses rejected or accepted by the SMTP server from the last call of an email-sending method, like SendEmail. Returns rejected email addresses if rejected is 1. Otherwise returns accepted email addresses.

Invalid email addresses identified by the SMTP server are stored in a bad email addresses list, while valid ones are stored in a good email addresses list within the object. Both lists reset automatically at the beginning of each new mail-sending call, allowing you to track which addresses were accepted or rejected.

Note: A the time of the SMTP session, the SMTP server can only verify the validity of an email address within its own domain because it has access to its internal user database or mailbox configuration. Addresses outside its domain, are implicitly accepted and the validity of the email address won't be discovered until arrives at the destination mail server.

Sends an RSET command to the SMTP server. This method is rarely needed. The RSET command resets the state of the connection to the SMTP server to the initial state (so that the component can proceed with sending a new email). The SmtpReset method would only be needed if a mail-sending method failed and left the connection with the SMTP server open and in a non-initial state. (A situation that is probably not even possible with the Chilkat mail component.)

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SmtpReset method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Sends a raw command to the SMTP server and returns the SMTP server's response. If non-us-ascii characters are included in command, then charset indicates the charset to be used in sending the command (such as utf-8, ansi, iso-8859-1, Shift_JIS, etc.)

If bEncodeBase64 is 1, then the response is returned in Base64-encoded format. Otherwise the raw response is returned.

Returns Nothing on failure

Creates an asynchronous task to call the SmtpSendRawCommand method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Authenticates with the SSH server using public-key authentication. The corresponding public key must have been installed on the SSH server for the sshLogin. Authentication will succeed if the matching sshUsername is provided.

Important: When reporting problems, please send the full contents of the LastErrorText property to support@chilkatsoft.com.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SshAuthenticatePk method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Authenticates with the SSH server using a sshLogin and sshPassword.

An SSH tunneling (port forwarding) session always begins by first calling SshTunnel to connect to the SSH server, then calling either AuthenticatePw or AuthenticatePk to authenticate.

Note: Once the SSH tunnel is setup by calling SshTunnel and SshAuthenticatePw (or SshAuthenticatePk), all underlying communcations with the POP3 or SMTP server use the SSH tunnel. No changes in programming are required other than making two initial calls to setup the tunnel.

Important: When reporting problems, please send the full contents of the LastErrorText property to support@chilkatsoft.com.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SshAuthenticatePw method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Closes the SSH tunnel for SMTP or POP3.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SshCloseTunnel method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Connects to an SSH server and creates a tunnel for SMTP or POP3. The sshHostname is the hostname (or IP address) of the SSH server. The sshPort is typically 22, which is the standard SSH port number.

An SSH tunneling (port forwarding) session always begins by first calling SshTunnel to connect to the SSH server, followed by calling either SshAuthenticatePw or SshAuthenticatePk to authenticate.

Note: Once the SSH tunnel is setup by calling SshOpenTunnel and SshAuthenticatePw (or SshAuthenticatePk), all underlying communcations with the SMTP or POP3 server use the SSH tunnel. No changes in programming are required other than making two initial calls to setup the tunnel.

Important: All TCP-based Internet communications, regardless of the protocol (such as HTTP, FTP, SSH, IMAP, POP3, SMTP, etc.), and regardless of SSL/TLS, begin with establishing a TCP connection to a remote host:port. External security-related infrastructure such as software firewalls (Windows Firewall), hardware firewalls, anti-virus, at either source or destination (or both) can block the connection. If the connection fails, make sure to check all potential external causes of blockage.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the SshOpenTunnel method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Adds an XML certificate vault to the object's internal list of sources to be searched for certificates and private keys when encrypting/decrypting or signing/verifying. Unlike the AddPfxSourceData and AddPfxSourceFile methods, only a single XML certificate vault can be used. If UseCertVault is called multiple times, only the last certificate vault will be used, as each call to UseCertVault will replace the certificate vault provided in previous calls.

Returns 1 for success, 0 for failure.

Uses an existing SSH tunnel for the connections to the POP3 andSMTP servers. This method is identical to the UseSshTunnel method, except the SSH connection is obtained from an SSH object instead of a Socket object.

Uses an existing SSH tunnel. This is useful for sharing an existing SSH tunnel connection wth other objects. (SSH is a protocol where the tunnel contains many logical channels. SMTP and POP3 connections can exist simultaneously within a single SSH tunnel as SSH channels.)

Returns 1 for success, 0 for failure.

Uses an existing SSH tunnel. This is useful for sharing an existing SSH tunnel connection wth other objects. (SSH is a protocol where the tunnel contains many logical channels. SMTP and POP3 connections can exist simultaneously within a single SSH tunnel as SSH channels.)

Returns 1 for success, 0 for failure.

Return 1 if a TCP/IP connection can be established with the POP3 server, otherwise returns 0.

Creates an asynchronous task to call the VerifyPopConnection method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Return 1 if a TCP/IP connection and login is successful with the POP3 server. Otherwise return 0.

Creates an asynchronous task to call the VerifyPopLogin method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Initiates sending an email, but aborts just after passing all recipients (TO, CC, BCC) to the SMTP server. This allows your program to collect email addresses flagged as invalid by the SMTP server.

Important: Please read this blog post before using this method: http://www.cknotes.com/?p=249>http://www.cknotes.com/?p=249

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the VerifyRecips method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Return 1 if a TCP/IP connection can be established with the SMTP server, otherwise returns 0.

Creates an asynchronous task to call the VerifySmtpConnection method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Return 1 if a TCP/IP connection and login is successful with the SMTP server. Otherwise returns 0.

Creates an asynchronous task to call the VerifySmtpLogin method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Enables a method call to be aborted by triggering the AbortCheck event at intervals defined by the HeartbeatMs property. If HeartbeatMs is set to its default value of 0, no events will occur. For instance, set HeartbeatMs to 200 to trigger 5 AbortCheck events per second.

VB6 Event callback implementation:

Important: Event callbacks from asynchronous method calls are generally not possible from the ActiveX. See VB6 Event Callbacks

Dim WithEvents myMailman As ChilkatMailMan

Private Sub myMailman_AbortCheck(abort As Long)

	'Insert application code here.

End Sub

This provides the percentage completion for any method involving network communications or time-consuming processing, assuming the progress can be measured as a percentage. This event is triggered only when it's possible and logical to express the operation's progress as a percentage. The pctDone argument will range from 1 to 100. For methods that finish quickly, the number of PercentDone callbacks may vary, but the final callback will have pctDone equal to 100. For longer operations, callbacks will not exceed one per percentage point (e.g., 1, 2, 3, ..., 98, 99, 100).

The PercentDone callback also acts as an AbortCheck event. For fast methods where PercentDone fires, an AbortCheck event may not trigger since the PercentDone callback already provides an opportunity to abort. For longer operations, where time between PercentDone callbacks is extended, AbortCheck callbacks enable more responsive operation termination.

To abort the operation, set the abort output argument to 1. This will cause the method to terminate and return a failure status or corresponding failure value.

VB6 Event callback implementation:

Important: Event callbacks from asynchronous method calls are generally not possible from the ActiveX. See VB6 Event Callbacks

Dim WithEvents myMailman As ChilkatMailMan

Private Sub myMailman_PercentDone(ByVal pctDone As Long, abort As Long)

	'Insert application code here.

End Sub

This event callback provides tag name/value pairs that detail what occurs during a method call. To discover existing tag names, create code to handle the event, emit the pairs, and review them. Most tag names are self-explanatory.

VB6 Event callback implementation:

Important: Event callbacks from asynchronous method calls are generally not possible from the ActiveX. See VB6 Event Callbacks

Dim WithEvents myMailman As ChilkatMailMan

Private Sub myMailman_ProgressInfo(ByVal name As String, ByVal value As String)

	'Insert application code here.

End Sub

Called from the background thread when an asynchronous task completes.

VB6 Event callback implementation:

Important: Event callbacks from asynchronous method calls are generally not possible from the ActiveX. See VB6 Event Callbacks

Dim WithEvents myMailman As ChilkatMailMan

Private Sub myMailman_TaskCompleted(task As ChilkatTask)

	'Insert application code here.

End Sub

This method is deprecated. Applications should instead call FetchAll.

Copy the email from a POP3 server into a EmailBundle. This does not remove the email from the POP3 server.

Returns Nothing on failure

Creates an asynchronous task to call the CopyMail method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

Marks multiple emails on the POP3 server for deletion. (Any email on the server having a UIDL equal to a UIDL found in uidlArray is marked for deletion.) To complete the deletion of the emails, a QUIT message must be sent and the POP3 session ended. This will happen automatically when the ImmediateDelete property equals 1, which is the default. If ImmediateDelete equals 0, then the Pop3EndSession method can be called to send the QUIT and end the session (i.e. disconnect.)

Note: When making multiple calls to a Delete* method, it's best to turn off ImmediateDelete, and then manually call Pop3EndSession to finalize the deletions.

Also, any method call requiring communication with the POP3 server will automatically re-establish a session based on the current property settings.

Returns 1 for success, 0 for failure.

Creates an asynchronous task to call the DeleteMultiple method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchOne.

Fetches an email by message number. WARNING: Be very careful if calling this method. Message numbers are specific to a POP3 session. If a maildrop has (for example) 10 messages, the message numbers will be 1, 2, 3, ... 10. If message number 1 is deleted and a new POP3 session is established, there will be 9 messages numbered 1, 2, 3, ... 9.

IMPORTANT: A POP3 connection must first be established by either calling Pop3BeginSession explicitly, or implicitly by calling some other method that automatically establishes the session. This method will not automatically establish a new POP3 session (because if it did, the message numbers would potentially be different than what the application expects).

Returns Nothing on failure

Creates an asynchronous task to call the FetchByMsgnum method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchByUidl.

Fetches an email from the POP3 mail server given its UIDL. Calling this method does not remove the email from the server. A typical program might get the email headers from the POP3 server by calling GetAllHeaders or GetHeaders, and then fetch individual emails by UIDL.

Returns a null reference on failure.

Returns Nothing on failure

Creates an asynchronous task to call the FetchEmail method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchUidlSet.

Given an array of UIDL strings, fetchs all the emails from the POP3 server whose UIDL is present in the array, and returns the emails in a bundle.

Returns Nothing on failure

Creates an asynchronous task to call the FetchMultiple method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchUidlSet.

Given an array of UIDL strings, fetchs all the email headers from the POP3 server whose UIDL is present in the array.

Note: The email objects returned in the bundle contain only headers. The attachments will be missing, and the bodies will be mostly missing (only the 1st numBodyLines lines of either the plain-text or HTML body will be present).

Returns Nothing on failure

Creates an asynchronous task to call the FetchMultipleHeaders method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This deprecated method will be removed in a future major release of Chilkat. MIME can potentially include non-encoded binary data and mixed character encodings, so downloading emails as a simple MIME string often requires processing and modifications, making it impractical. Instead, applications should use FetchMimeBd or methods that download emails to email objects.

This method downloads emails from the POP3 server for each UIDL in uidlArray and returns an object containing the collection of downloaded MIME strings.

Returns Nothing on failure

Creates an asynchronous task to call the FetchMultipleMime method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchOne.

Fetches a single header by message number. Returns an email object on success, or a null reference on failure.

Returns Nothing on failure

Creates an asynchronous task to call the FetchSingleHeader method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchByUidl.

Fetches a single header by UIDL. Returns an email object on success, or a null reference on failure.

Note: The email objects returned in the bundle contain only headers. The attachments will be missing, and the bodies will be mostly missing (only the 1st uidl lines of either the plain-text or HTML body will be present).

Returns Nothing on failure

Creates an asynchronous task to call the FetchSingleHeaderByUidl method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchAll.

Retrieves all emails from the POP3 server, limiting the body to the first numBodyLines lines and excluding attachments. The returned emails are valid objects with truncated bodies and no attachments.

Returns Nothing on failure

Creates an asynchronous task to call the GetAllHeaders method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchFull.

If a partial email (header-only) is retrieved using GetHeaders or GetAllHeaders, this method will download and return the full email from the server using the partial email as an argument.

Returns Nothing on failure

Creates an asynchronous task to call the GetFullEmail method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchRange.

The same as the GetAllHeaders method, except only the emails from fromIndex to toIndex on the POP3 server are returned. The first email on the server is at index 0.

Returns Nothing on failure

Creates an asynchronous task to call the GetHeaders method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Applications should instead call GetServerCert.

Returns the POP3 server's SSL certificate. This is available after connecting via SSL to a POP3 server. (To use POP3 SSL, set the PopSsl property = 1.)

Returns a null reference if no POP3 SSL certificate is available.

Returns Nothing on failure

This method is deprecated. Applications should instead call GetServerCert.

If using SSL/TLS, this method returns the SMTP server's digital certificate used with the secure connection.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchUidls.

Returns the UIDLs of the emails currently stored on the POP3 server.

Returns Nothing on failure

Creates an asynchronous task to call the GetUidls method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This method is deprecated. Call GetLastJsonData instead.

Provides information about what transpired in the last method called on this object instance. For many methods, there is no information. However, for some methods, details about what occurred can be obtained by getting the LastJsonData right after the method call returns.

Returns Nothing on failure

This deprecated method will be removed in a future Chilkat major version. Applications should instead call the email object's LoadEml method.

Loads a .eml file containing an email.

Returns Nothing on failure

This method is deprecated. Applications should instead call LoadMbxFile.

Loads a .mbx file containing emails and returns an email bundle. If a Filter is present, only emails matching the filter are returned.

Returns Nothing on failure

This deprecated method will be removed in a future Chilkat major version. Applications should instead call the email object's SetFromMimeText method.

Creates and loads an email from a MIME string. Returns a null reference on failure.

Returns Nothing on failure

This deprecated method will be removed in a future Chilkat major version. Applications should instead call the email object's SetFromXmlText method.

Loads an XML file containing a single email and returns an email object. Returns a null reference on failure.

Returns Nothing on failure

This deprecated method will be removed in a future Chilkat major version. Applications should instead call the email object's SetFromXmlText method.

Loads an XML string containing a single email and returns an email object. Returns a null reference on failure.

Returns Nothing on failure

This deprecated method will be removed in a future Chilkat major version. Applications should instead call the email bundle object's LoadXml method.

Loads an XML file containing one or more emails and returns an email bundle. If a Filter is present, only emails matching the filter are returned. Returns a null reference on failure.

Returns Nothing on failure

This deprecated method will be removed in a future Chilkat major version. Applications should instead call the email bundle object's LoadXmlString method.

Loads from an XML string containing emails and returns an email bundle. If a Filter is present, only emails matching the filter are returned.

Returns Nothing on failure

This deprecated method will be removed in a future Chilkat major version. Applications should instead use the Chilkat Dns class to do MX lookups.

Performs a DNS MX lookup to return the mail server hostname based on an email address.

Returns Nothing on failure

This deprecated method will be removed in a future Chilkat major version. Applications should instead use the Chilkat Dns class to do MX lookups.

Performs a DNS MX lookup to return the list of mail server hostnames based on an email address. The primary server is at index 0. In most cases, there is only one mail server for a given email address.

Returns Nothing on failure

This method is deprecated. Applications should instead call FetchAll.

Downloads and removes all email from a POP3 server. A bundle containing the emails is returned. A null reference is returned on failure.

Returns Nothing on failure

Creates an asynchronous task to call the TransferMail method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure

This deprecated method will be removed in a future major release of Chilkat. MIME can potentially include non-encoded binary data and mixed character encodings, so downloading emails as a simple MIME string often requires processing and modifications, making it impractical. Instead, applications should use FetchMimeBd or methods that download emails to email objects.

Same as FetchMultipleMime except that the downloaded emails are also deleted from the server. Returns a null reference on failure.

Returns Nothing on failure

Creates an asynchronous task to call the TransferMultipleMime method with the arguments provided.

Note: Async method event callbacks happen in the background thread. Accessing and updating UI elements existing in the main thread may require special considerations.

Returns Nothing on failure