Add SES newsletter delivery (experimental)#792
Draft
lylo wants to merge 1 commit into
Draft
Conversation
Feature-flagged per blog (ses_newsletter_delivery) to run in parallel with Postmark during warm-up. Includes Email::Suppression list for bounce/complaint handling, SQS polling job, region failover, admin suppressed emails management, and AWS provisioning rake tasks.
lylo
force-pushed
the
main
branch
2 times, most recently
from
c853070 to
18e4461
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ses_newsletter_delivery) — Postmark remains the default pathsend.pagecord.com(separate domain from Postmark'snewsletters.pagecord.com)Email::Suppressionrecords that block future sendsEmailSubscriberrecords stay intact — only the suppression list prevents delivery/admin/suppressed_emailsfor viewing and unsuppressing emailseu-west-2→eu-west-1ses:provision) automates full AWS setupWhat's new
Email::Suppression,Email::EventPostDigest::SesDelivery(mirrorsPostmarkDelivery)Email::ProcessBouncesJob(SQS polling, every 5 min)/admin/suppressed_emails— list, filter, unsuppressses:provision,ses:statusses_newsletter_deliveryinconfig/features.rbdocs/ses-newsletter-delivery.mdWhat's unchanged
PostDigestMailer+ Premailer) is reused as-isPostDigest::PostmarkDeliveryis untouched and remains the defaultRollout plan
Deploys inactive — no blogs have the feature flag. Gradual enablement:
Test plan
ses:provisionand add DNS recordssuccess@simulator.amazonses.com— verify delivery + event recordsbounce@simulator.amazonses.com— verify suppression createdcomplaint@simulator.amazonses.com— verify complaint suppressionsend.pagecord.com)