The Tech Dragon / Knowledgebase / Tech Dragon Mail Conduit / What Tech Dragon Mail Conduit Does — and Does Not Do
Knowledgebase // Tech Dragon Mail Conduit

What Tech Dragon Mail Conduit Does — and Does Not Do

Product Knowledgebase View Plugin

Tech Dragon Mail Conduit solves one specific WordPress mail problem: it lets supported MailPoet sending hand off to WordPress mail so the site's existing compatible mail-delivery plugin can handle transport.

What Tech Dragon Mail Conduit does

The conceptual path is:

MailPoet → Tech Dragon Mail Conduit → WordPress wp_mail() → existing mail-delivery / SMTP plugin

  • Routes supported MailPoet messages through the WordPress mail path.
  • Preserves supported message details during the handoff, including HTML/plain-text content, sender and reply-to information, content type, and unsubscribe headers.
  • Includes recursion protection so Tech Dragon Mail Conduit does not loop its own handoff back through itself.
  • Uses compatibility and failure safeguards so Tech Dragon Mail Conduit does not take over the MailPoet send path when required checks fail.
  • Provides a minimal operational status in Free, with deeper diagnostics in Pro.

What Tech Dragon Mail Conduit does not do

  • It is not an SMTP server or SMTP provider.
  • It does not store or manage SMTP usernames, passwords, API keys, or provider credentials.
  • It does not configure SPF, DKIM, DMARC, DNS, or domain authentication.
  • It does not replace MailPoet.
  • It does not replace the downstream mail-delivery plugin.
  • It does not guarantee inbox placement or delivery after WordPress hands the message to the downstream transport.
  • It is not intended to become a general-purpose email log.

Where Tech Dragon Mail Conduit's responsibility ends

Tech Dragon Mail Conduit's owned path ends when the supported MailPoet message has been handed successfully to WordPress wp_mail(). From there, your downstream mail-delivery plugin and provider own transport, authentication, provider responses, and final delivery behavior.

Why this boundary matters

Keeping the boundary narrow makes troubleshooting clearer. If the handoff into wp_mail() succeeds but a message later fails at the provider, that is a downstream transport problem—not a Tech Dragon Mail Conduit bridge failure.

Fuel the Dragon