Notification paths
Let users choose the reason they want email.
Logister splits project notifications into error triage, project health, workflow routing, digest summaries, delivery limits, and operational notices. SES is only the delivery layer; project users still choose their own purpose-based settings.
Email delivery
SES is configured through ordinary SMTP environment variables.
Logister does not need checked-in provider secrets. Self-hosters put SMTP host, port, domain, username, password, sender, and reply-to values in their deploy provider's secret/config store. The deployment reference explains each sample entry and which provider values to use.
Deliverability
Branded, useful mail is less likely to be treated as noise.
Error emails include project, environment, release, occurrence, and triage links when available. That helps recipients understand why the message was sent and makes the email more useful than a generic exception dump. Operators should also configure SES identity verification, SPF, DKIM, DMARC, and a sending domain that matches the self-hosted instance.
Worker requirement
Keep Sidekiq running for project mail.
Email delivery, immediate alerts, digest scheduling, monitor notifications, and operational notices run through background jobs. A self-hosted deployment should run at least one Sidekiq worker alongside the Rails web process.
Verify
Test provider delivery and Logister routing separately.
- Verify the SES identity, SPF, DKIM, DMARC, sender, and reply-to settings outside Logister.
- Set the Rails SMTP environment variables in the deploy secret store.
- Send or trigger one account email to confirm baseline SMTP delivery.
- Enable one project error notification or digest for a project user.
- Trigger a controlled event and confirm Sidekiq delivers the expected project email.