Integration

Custom SMTP integrations on Wodby

Use Custom SMTP to connect any standards-compatible SMTP server to Wodby as a reusable outbound relay. Configure the upstream host, secure transport, port, and optional credentials once, then attach the integration to OpenSMTPD so application stacks can send mail without embedding relay settings in app code.

SMTP

Bring any SMTP relay

Connect an SMTP service that is not represented by a dedicated Wodby provider, including hosted mail platforms and organization-managed relay servers.

Keep relay transport secure

Use mandatory STARTTLS or implicit TLS and override the standard relay port when the upstream server requires it.

Reuse one mail route

Store relay settings and optional credentials in one integration, then attach the same outbound delivery path wherever it is needed.

Supported workflows

How Custom SMTP fits into Wodby

Each supported integration kind maps Custom SMTP into a specific part of the delivery workflow, whether that means pulling source code, running pipelines, relaying email, connecting managed services, or injecting provider credentials into workloads.

SMTP

Custom SMTP

Connect OpenSMTPD to any standards-compatible upstream SMTP server and reuse that relay configuration across Wodby application stacks.

  • Set the upstream relay hostname, with port 587 and mandatory STARTTLS used by default.
  • Choose implicit TLS for servers that require SMTPS, commonly on port 465, and add credentials only when the relay requires authentication.
  • Attach the integration to OpenSMTPD so applications can send internally on port 25 while OpenSMTPD handles upstream delivery.

Related features

Explore the surrounding workflow

This provider usually sits next to stack-based delivery, backup workflows, managed databases, or integration-backed configuration. These pages cover the product surfaces most relevant to Custom SMTP.

See integration workflows

Keep SMTP providers reusable across stacks and environments.

Browse all integrations

Compare this provider with the rest of the integration catalog and other supported workflows.

Stack fit

Stacks that commonly pair with Custom SMTP

Wodby does not treat integrations as isolated setup screens. They become part of stack delivery, so the strongest matches are the stacks where this provider solves a repeated operational problem.

  • SMTP server stack that can relay mail directly or integrate with third-party delivery providers for reliable sending.

    OpenSMTPD is the direct stack match: applications send mail to it internally, and it forwards messages through the configured Custom SMTP relay.

    View stack
  • WordPress application stack for self-hosted websites, multisite setups, and repeatable client environments.

    WordPress projects can centralize transactional email delivery without copying upstream SMTP credentials into every site.

    View stack
  • Drupal 11 application stack for modern self-hosted websites and multi-environment Drupal delivery.

    Drupal environments can share a stack-managed relay path while keeping mail delivery configuration outside the application repository.

    View stack
  • Laravel

    Stack

    Laravel application stack for teams that want a reusable setup for web, worker, and queue-based PHP projects.

    Laravel applications can send through OpenSMTPD while Wodby keeps upstream relay settings reusable across environments.

    View stack

Compare providers or keep reading

Use the catalog to compare other providers with the same integration kind, or read the broader feature pages to understand how integrations fit into Wodby stacks, CI/CD, backups, and managed services.