How Tech Dragon Mail Conduit Routes MailPoet Through wp_mail()

Tech Dragon Mail Conduit is designed around a narrow handoff path rather than a second mail transport stack.

The mail path

For supported MailPoet messages, the intended path is:

MailPoet → Tech Dragon Mail Conduit → WordPress wp_mail() → downstream mail-delivery plugin → provider

1. MailPoet creates the message

MailPoet remains responsible for the MailPoet workflow: newsletters, notifications, automations, subscriber context, and the message data it prepares.

2. Tech Dragon Mail Conduit evaluates whether it can safely bridge the message

Tech Dragon Mail Conduit applies its compatibility and safety checks before taking over the supported handoff. If required checks fail, its safety model is designed to avoid taking control of the send path rather than forcing an uncertain conversion.

3. Supported message data is preserved

The Free edition includes message-preservation behavior for supported details such as HTML and plain-text content, sender and reply-to information, content type, and unsubscribe headers.

4. Tech Dragon Mail Conduit hands the message to wp_mail()

After conversion, Tech Dragon Mail Conduit hands the message to WordPress wp_mail(). This is the standard WordPress mail path used by many SMTP and mail-delivery plugins.

5. Your mail-delivery plugin takes over

The downstream plugin then performs whatever work it normally owns: SMTP/API transport, provider authentication, delivery logging, retries, provider responses, or other transport-specific behavior.

Recursion protection

Because Tech Dragon Mail Conduit deliberately hands a MailPoet-originated message into WordPress mail, recursion protection is part of the bridge's required safety behavior. Tech Dragon Mail Conduit must be able to distinguish the message it is handing off from a new MailPoet send event so the bridge does not repeatedly process the same message.

Failure boundaries

A successful Tech Dragon Mail Conduit handoff does not mean the provider accepted or delivered the message. Conversely, a provider rejection after wp_mail() does not automatically indicate a Tech Dragon Mail Conduit failure. Use Troubleshooting Tech Dragon Mail Conduit to identify which layer owns the failure.