Repository navigation
fix(backlinks): block restricted email senders - #31
Merged
Merged
Conversation
ThreatCrush Security Scan16 finding(s) HIGH/CRITICAL: 13 | MEDIUM: 3
Snippets are redacted; ThreatCrush never prints matched credential material. |
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.
Scope
Add a configurable sender blocklist to the Backlinks follow-up sender before it calls SMTP or Mailgun. Pending campaign records are preserved; this does not redirect traffic to another provider.
Verification
node --test mcp_modules/backlinks/test/sending.test.js— 1 testThe guard only takes effect after
EMAIL_QUEUE_BLOCKED_SENDERSis configured in the deployed service. No production configuration was changed.