hackclub / hackclub/hcb

[ActionMailer] Use separate SMTP infrastructure for critical/transactional/marketing

Open
#13,101 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
870
Forks
138
Avg merge
1d 14h
Merged PRs (30d)
208

Description

Examples:
- critical
- login
- security-related emails
- transactional
- new transactions
- most of our emails
- and _maybe_ end of month summaries. These are transactional by definition, but maybe it's better to have it run through our marketing system
- marketing
- HCB announcements

The idea is to protect our email deliverability reputation (in the case that people send junk through HCB announcements). Any bulk UGC emails should go through the marketing infra.

In addition, we should explore fallbacks. For example, if critical SMTP fails, we fallback to transactional SMTP, which fallsback to marketing??

Maybe we want to explore dedicated IP if it's reasonably priced.

Contributor guide

Open the contributing guide

Research direction

Start at the ActionMailer configuration and inventory the email paths represented by critical, transactional, and marketing messages. Clarify whether bulk UGC belongs on marketing infrastructure, which fallback order is required, and whether dedicated IPs are in scope. Done requires an agreed infrastructure design; the issue names no files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.