Skip to content

Use dedicated Rowset domain for transactional email - #419

Merged
gregagi merged 1 commit into
mainfrom
fix/rowset-transactional-email
Oct 7, 2026
Merged

gregagi merged 1 commit into
mainfrom
fix/rowset-transactional-email

Conversation

@gregagi

@gregagi gregagi commented Oct 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Use dedicated mg.rowset.app for all Django/allauth transactional emails, with Rowset <rasul@rowset.app> sender and environment overrides.
  • Document both-service configuration, scoped credential storage, verification, and rollback; leave signup rules and newsletter integrations unchanged.
  • Cover sender defaults and signup/confirmation/password-reset/existing-account email adapter wiring.

Verification

  • Regression reproduced against the previous LVTD sender defaults, then five focused tests passed (external MJML renderer mocked for unit tests).
  • Ruff and diff checks passed. Full backend/frontend/CLI checks run in CI.
  • Mailgun domain active, all five required DNS records valid, tracking disabled; operator-inbox domain smoke email passed SPF/DKIM/DMARC.
  • Production runtime/account-email delivery checks follow deployment. No customer test email, Listmonk, or newsletter setup.

@gregagi
gregagi merged commit d3374f7 into main Oct 7, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant