Operating System

Linux

OS Version

Rocky Linux 10

System Architecture

x86_64

Docker Version

Docker version 29.1.3, build f52814d

Docker Compose Version

No response

Reproducible in Latest Version?

Yes, occurs in the latest stable release

Reproduction Steps

1. Configure the server to send outbound emails using its own/local SMTP (direct delivery / local MTA).
2. Send a test email to an external address (e.g., Gmail) and confirm it is delivered successfully.
3. Go to the SMTP/Relay settings page and add an SMTP relay (e.g., SES/third-party relay).
4. (Optional) Ensure the relay is active and send another test email to confirm relay sending works.
5. Disable (inactivate) or delete the relay from the UI.
6. Send a new outbound email from the system to an external address.

Observed Behavior

• After the relay is disabled/deleted, outbound emails do not send via the server’s own/local SMTP anymore.
• The system appears to still route outbound mail through the relay (or a stale relay configuration), even though the relay is removed/inactive.
• Emails fail/bounce (or remain queued) because:
  • the relay is no longer available, or
  • relay authentication is missing, or
  • the relay configuration is partially retained.
• Result: outbound email delivery breaks until the relay is re-added/re-enabled or the configuration is manually corrected.

Expected Behavior

• When a relay is disabled/inactive or deleted, the system should immediately stop using it for outbound delivery.
• Outbound email should automatically fall back to the server’s own/local SMTP (or the default delivery method).
• Sending should succeed using local SMTP without requiring relay credentials/config.
• UI state and actual routing should match: inactive/deleted relay must not affect delivery.

Supplemental Information