fix: address the blast copy to team@, which Email Routing delivers - #8
Merged
Merged
Conversation
Both blast paths bcc the real recipients and put events@purduehackers.com in the To, so that address is only ever the copy we keep. It has no Email Routing rule on the zone — team@purduehackers.com is the one that does — so the copy was addressed to somewhere nothing delivers. Same reasoning as the reply-to, applied to the other half of the envelope. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AHAyCUvMbU4jG9bg5EuC3C
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
Pull request overview
This PR fixes where the internal “copy” of outgoing event blast emails is delivered by updating the to address (the real recipients are BCC’d) to an address that is covered by the domain’s Email Routing rules.
Changes:
- Update event blast sending (
Eventscollection) to send the internal copy toteam@purduehackers.cominstead ofevents@purduehackers.com. - Update manual email blast sending (
Emailscollection) to send the internal copy toteam@purduehackers.com. - Add clarifying inline comments explaining why the
tofield must be a routable address.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/collections/Events.ts | Routes the blast “To” copy to team@purduehackers.com so the kept copy is actually delivered. |
| src/collections/Emails.ts | Routes the manual blast “To” copy to team@purduehackers.com for consistent deliverability. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Both blast paths bcc the real recipients and put
events@purduehackers.comin the To, so that address is only ever the copy we keep for ourselves. It has no Email Routing rule on the zone —team@purduehackers.comis the address that does — so that copy was going to an address nothing delivers.Same reasoning as the reply-to in #7, applied to the other half of the envelope.
tsc --noEmitandprettier --checkclean.🤖 Generated with Claude Code
https://claude.ai/code/session_01AHAyCUvMbU4jG9bg5EuC3C