Smtp

Custom SMTP delivers this environment's authentication email through any relay you already operate: verification, invitations, magic links, and one-time codes. A newly connected provider becomes the one that sends. Other connected email providers stay as fallbacks after a hard failure. Authdog's managed provider sends when none of yours is active.

Prepare the relay

Collect the submission host, port, username, and password from the relay. Use one of these transports:

• Port 587, which upgrades with STARTTLS. Leave Use TLS/SSL off.
• Port 465 with Use TLS/SSL on, for implicit TLS.

Authdog authenticates with AUTH LOGIN when both username and password are set. Do not point this form at an unencrypted SMTP endpoint.

Verify the From address with the relay, and publish SPF and DKIM for that domain. Authdog does not verify domain ownership for you.

Connect SMTP

In the Authdog console:

1. Select the project and environment.
2. Open Notifications > Providers.
3. Select the Email channel.
4. Choose Custom SMTP and select Connect.
5. Enter:

6. Save. This relay becomes the active provider.
7. Select Test, enter a recipient outside your own domain, and confirm delivery.

The password is encrypted and is not loaded back into the browser. On a later edit, leave it blank to keep the stored password. Enter a new value only to replace it.

Use Set active if you connected SMTP but another provider is still in use. Use managed returns delivery to Authdog.

Set the visible From name and Reply-to under Notifications > Configuration. Those defaults apply to every template, independent of which provider sends.

Test it

1. Send the provider test. A refused connection usually means the host, port, or TLS mode does not match the relay.
2. Trigger a real template, such as a magic link or an invitation, in the same environment.
3. Confirm the send appears under Notifications > Events.

Use a separate credential and from-address for production. Provider configuration does not copy between environments.

Related