Add Reply-To header to contact form email notifications #5
No reviewers
Labels
No labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
javascript
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Snupai/snupai-site!5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "copilot/fix-9fe61eec-3938-4954-ae97-5faf43c62bbb"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
The contact form backend was sending email notifications without a Reply-To header, causing replies to go to the SMTP user account instead of the person who submitted the form. This made it difficult to respond directly to contact form submissions.
Solution
Added a
replyTofield to thetransporter.sendMail()configuration insrc/app/api/contact/route.tsthat uses the validated email address from the form submission.Changes
replyTo: email,in the email configurationemailvariable from the form dataImpact
Before: Replies to contact form notifications went to the SMTP user (e.g.,
noreply@domain.com)After: Replies now go directly to the form submitter's email address
This enables natural email conversations with people who contact you through the website form.
Testing
Closes the issue regarding Reply-To header functionality in contact form emails.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.
The latest updates on your projects. Learn more about Vercel for Git ↗︎