Configuring an Email Relay

This article walks through adding a new relay client. The exact fields vary by provider, but the pattern is the same: pick a provider, supply credentials, validate, set defaults.

Step-by-Step

1. Go to Architect Panel → Email Relay Clients and click Add Relay.
2. Select the provider type from the dropdown.
3. Enter the credentials:
   • SMTP: host, port, encryption (TLS / STARTTLS), username, password.
   • SendGrid / Postmark / SES API: API key (and AWS region for SES).
4. List the sender domains this relay is authorised for (e.g. yourcompany.com). Outgoing mail from other domains will route via a different relay if available.
5. Set the daily and per-minute send limits if you want a safety cap.
6. Click Send Test Email — choose a recipient and observe delivery.
7. If everything looks good, tick Make default for the relevant scope (global, tenant or per-template).

DNS Records to Set

For reliable deliverability, regardless of provider, publish:

• SPF: Authorises the relay's IPs to send for your domain.
• DKIM: Cryptographic signing — the relay gives you a public key to publish.
• DMARC: Tells receiving servers what to do with unauthorised mail. Start with p=none and graduate to p=quarantine once you've verified all traffic.

Examples

• Office 365 SMTP relay: host smtp.office365.com, port 587, STARTTLS, mailbox credentials. Limited to 30 messages/minute.
• SendGrid API: API key, supports tagged events for marketing dashboards.
• AWS SES sandbox: Only sends to verified recipients until production access is granted by AWS Support.

Warning: Test the relay before setting it as default for production. A misconfigured relay can dump every outbound notification into spam folders for days while the IP reputation recovers.