Repository navigation
docs(deliverability): route SES Integrations to dedicated IPs through a configuration set - #47
Merged
Merged
Conversation
… a configuration set Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Merged
2 of 4 tasks
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
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.
Follows getsphericon/sphericon#1535 (an SES Integration may name a configuration set, getsphericon/sphericon#1463).
A new section, "Dedicated IPs on Amazon SES": one SES Integration per stream (the transactional one as the email default, the marketing one chosen on broadcasts and automation email steps), each with its own configuration set; a manual Provider limit on each so the two stay within the account quota; the save-time check and its warning.
🤖 Generated with Claude Code