Direct Mail:SingleSendMail

The sender address configured in the management console.

The address type. Valid values:

• 0: random account

• 1: sender address

The tag created in the DirectMail console. Tags are used to categorize email batches. You can query the sending status of each batch by tag. If the email tracking feature is enabled, you must use an email tag when sending emails. The value must be 1 to 128 characters in length and can contain letters, digits, underscores (_), and hyphens (-).

Specifies whether to use the reply-to address configured in the management console (the address must be verified). Valid values: true or false.

The destination address. You can specify multiple email addresses separated by commas. A maximum of 100 addresses are supported (mailing lists are supported).

The email subject. The value cannot exceed 256 characters in length.

The HTML body of the email.

Note: HtmlBody and TextBody are used for different types of email content. You must specify one of them.

• The size limit for URL-based parameter passing is approximately 80 KB.

• The size limit for Body-based parameter passing with the new SDK is approximately 8 MB (Java 1.4.0 or later, Python3 1.4.0 or later, PHP 1.4.0 or later).

The text body of the email.

Note: HtmlBody and TextBody are used for different types of email content. You must specify one of them.

• The size limit for URL-based parameter passing is approximately 80 KB.

• The size limit for Body-based parameter passing with the new SDK is approximately 8 MB (Java 1.4.0 or later, Python3 1.4.0 or later, PHP 1.4.0 or later).

The sender nickname. The value cannot exceed 15 characters in length.

For example, if the sender nickname is set to "Jane" and the sender address is test***@example.net, the recipient sees the sender address as "Jane" test***@example.net.

The reply-to address.

The reply-to address nickname.

Specifies whether to enable data tracking. Valid values:

• 1: Enable data tracking.

• 0 (default): Disable data tracking.

The type of unsubscribe link. Valid values:

• disabled: No unsubscribe link is generated.

• default: The default policy is used. An unsubscribe link is generated when emails are sent from batch-type sender addresses to specific domains, such as those containing keywords "gmail", "yahoo", "google", "aol.com", "hotmail", "outlook", or "ymail.com". For more information, refer to Unsubscribe link generation and filtering mechanism.

The display language is automatically detected based on the recipient's browser settings.

The filtering level. For more information, refer to Unsubscribe link generation and filtering mechanism.

Valid values:

• disabled: No filtering is applied.

• default: The default policy is used. Batch addresses use sender address-level filtering.

• mailfrom: Sender address-level filtering.

• mailfrom_domain: Sender domain-level filtering.

• edm_id: Account-level filtering.

The email header settings.

Both standard and non-standard fields must comply with the syntax requirements for headers defined in the standard. A maximum of 10 headers can be passed through the headers field when sending emails via API. Headers exceeding this limit are ignored. SMTP has no such limit.

1. Standard fields

Message-ID, List-Unsubscribe, List-Unsubscribe-Post

Standard fields overwrite the original values in the email header.

2. Non-standard fields

Case-insensitive.

a. Fields prefixed with X-User- (not pushed to EventBridge or Message Service MNS. This is an API-only requirement. SMTP allows any custom fields.)

b. Fields prefixed with X-User-Notify- (pushed to EventBridge and Message Service MNS. Both API and SMTP are supported.)

When pushed to EventBridge or MNS, these fields are included under the header field.

The ID of the dedicated IP address pool. Users who have purchased dedicated IP addresses can use this parameter to specify the outbound IP address for this email. For more information, refer to Dedicated IP.

• Specifies the BCC (blind carbon copy) recipient list for the email.

• The system sends a copy identical to the main email content to each BCC address. The BCC information is not visible to any recipients (including ToAddress and BccAddress).

• To protect the privacy of BCC recipients, email tracking features are disabled by default for BCC emails. This means the system does not record behavioral data such as open rates or click-through rates for BCC emails. However, billing for sending volume, sending details, and sending status statistics remain consistent with regular emails.

• A maximum of 2 BCC recipients can be specified per send.

Note: The SingleSendMail operation does not support the Cc (carbon copy) field. Use SMTP if you need this feature.

Specifies whether to enable domain-level authentication. Valid values:

• true

• false

Use this parameter only for domain-level authentication. Ignore it for sender address-level authentication.

1. Create the address domain-auth-created-by-system@example.com in the console. Keep the prefix before @ unchanged and use your own domain name as the suffix.

API scenario

Set AccountName to a custom sender address for the domain. The recipient sees the custom sender address as the sender.

SMTP scenario

a. Set the domain password through the ModifyPWByDomain operation.

b. Authenticate using the domain name and the configured password. Pass a custom address such as user@example.com as the actual sender (mailfrom). The recipient sees user@example.com as the sender.