Katalyst: Verifying Katalyst email notifications after configuration changes

Description

• After infrastructure changes (mail server migration, password rotation, port changes), Katalyst email notifications stop working.
• Typical symptoms:
  • No emails on experiment creation, assignment, or workflow transitions.
  • No obvious error in the Katalyst UI, but server logs may show SMTP‑related failures.
• It is unclear whether Katalyst or the mail server configuration is the cause.

Solution

• Review and update the Katalyst email configuration to match current mail server settings:
  • SMTP hostname and port.
  • Encryption type (TLS/SSL/plain).
  • Authentication method and credentials.
  • Sender address and allowed relay rules.
• On the mail server side, confirm that:
  • The Katalyst server host/IP is allowed to relay messages.
  • Any new security policies (e.g., SPF/DKIM/DMARC, IP allow‑lists) are satisfied.
• Use a controlled test:
  • Configure a known‑good recipient address (internal mailbox).
  • Trigger a simple notification (e.g., create a test experiment).
  • Check Katalyst logs for any email errors and verify message delivery in the mailbox.

Once verified, document the configuration and responsible teams (application vs. mail administrators) to streamline future changes.