SMTP
Deliver the platform's own transactional mail over SMTP
Lunogram sends two kinds of email, configured in two different places:
| Sent by | Configured in | |
|---|---|---|
| Platform mail — password resets, project invitations and account notices | the deployment itself | the node configuration |
| Project mail — campaigns, journeys and broadcasts | a project's email provider | the console, per project |
SMTP is one of the two channels for platform mail. Project mail goes through a provider integration.
Platform mail
mail:
channel: smtp
from:
address: no-reply@example.com
smtp:
host: smtp.example.com
port: 587
username: lunogram
password: "${SMTP_PASSWORD}"
tls: starttlsAny SMTP-compatible service works. See Sending mail for the full reference, including the webhook channel and how to override the messages.
| Provider | Host | Port |
|---|---|---|
| Gmail | smtp.gmail.com | 587 |
| Outlook | smtp-mail.outlook.com | 587 |
| Yahoo | smtp.mail.yahoo.com | 587 |
| Fastmail | smtp.fastmail.com | 587 |
Most personal email providers cap sending at 100–500 messages a day. That is ample for platform mail, which is a handful of messages per admin, but it is not a campaign sender.
Project mail
Project providers are WASM modules, and a module reaches the network through the host's HTTP function. The sandbox offers no raw TCP socket, so a provider module cannot speak SMTP.
Configure an HTTP provider instead — Resend, Mailgun, SendGrid or Amazon SES — or the webhook provider, which posts each message to an endpoint of yours that may relay it however you like, SMTP included.