Repository navigation
Forward inbound SMS alerts through Resend, not Mailgun - #266
Merged
Merged
Conversation
Mailgun is being shut off (its charge was declined; the fleet sends through Resend, and qrypt's own Supabase auth already does). This was the app's last Mailgun sender. - SMSAlertEmailService (src/lib/services/sms-alert-email-service.js) replaces MailgunEmailService: same sendEmail / sendSMSWebhookAlert / formatter interface, POSTs to api.resend.com, injectable fetch for tests. Configured from RESEND_API_KEY; FROM_EMAIL / OTP_TO_EMAIL unchanged. - Drops mailgun.js and form-data; the Mailgun unit test and both integration tests (one was quarantined) are replaced by tests/sms-alert-email-service.test.js. - .env.example and scripts/supabase-email.sh default to smtp.resend.com. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan13 finding(s) MEDIUM: 9 | LOW: 4
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
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.
Mailgun is being shut off: the account's charge was declined, and the fleet already sends through Resend. qrypt's own Supabase auth sends through smtp.resend.com too. This was the app's last Mailgun sender: the Telnyx inbound-SMS webhook emails each message (OTP codes) to
otp@qrypt.chat.SMSAlertEmailServicereplacesMailgunEmailService. It has the same interface (sendEmail,sendSMSWebhookAlert, formatter,createSMSWebhookEmailService) and POSTs toapi.resend.com/emails.RESEND_API_KEYreplacesMAILGUN_API_KEY/MAILGUN_DOMAIN;FROM_EMAIL(hello@qrypt.chat) andOTP_TO_EMAILare unchanged.resend._domainkeyandsend./rsend.are in Porkbun. The apex MX stays on Forward Email.mailgun.jsandform-dataare removed. The old Mailgun unit test and two integration tests (one quarantined) are replaced bytests/sms-alert-email-service.test.js: payload shape, bearer auth, Resend refusal → failure result, OTP forwarding, no key → disabled..env.exampleandscripts/supabase-email.shnow default to Resend SMTP.Tests: 553/553 across 88 files.
🤖 Generated with Claude Code