Send a transactional message through MailPace

Use the language library or maintained SMTP client linked from MailPace’s documentation. Match the client to the current send reference rather than copying historical OhMySMTP examples without reviewing the migration guidance.

Submit an approved transactional message

1. Load the verified domain’s credential from secure backend configuration.
2. Select a sender on that domain and one controlled recipient.
3. Supply subject and text/HTML according to the current library’s field names; do not assume another provider’s text/html properties map unchanged.
4. Submit once and retain the returned message/correlation identity with your application operation.

For SMTP, use the documented host, credential, and TLS mode. Keep certificate validation enabled. MailPace’s transactional-only policy applies regardless of whether the submission uses HTTP or SMTP.

Inspect the result and limits

Check provider activity and the controlled inbox. The documentation distinguishes recipient limits and lack of batch-email support; do not convert a multi-recipient request into an assumed per-recipient batch API.

Set bounded retry behavior and investigate unknown acceptance after timeouts. A successful API call does not establish inbox placement. Handle bounces and complaints according to the provider’s feedback facilities before production.

MailKite can provide a separately configured reply-receiving path, but it does not inherit MailPace’s message IDs or credentials. Choose one sending transport per operation during migration.