Improve notification email headers to route auto-replies to the relevant user
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
I've set up my nextcloud to use a dedicated smtp account to send notifications.
So if i'm sharing a file or calenderevent the recipient recieves a mail from MyUser Name via MyCloud <cloud@myclouddomain.com>
If that recipent tries to answer to that e-mail the cloud-user recives the answer because the mail contains a Reply-To-Header: user@arbitraridomain.com.
So far so good.
If on the other hand the recipient has set up an auto-reply (out of office) notification: that will be delivered to cloud@mydomain.com and will never be read by the cloud-user.
- can somebody elaborate on weather that's due to the
From-Header or theReturn-Path-Header?
according to rfc3834 the Return-Path should be used. - would it be possible or advisable to set the Return-Path value to the same value as the Reply-To value without running into issues with DKIM / SPF and Spamfilters?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading RFC 3834 and tracing where notification emails are assembled; the issue names no specific file or test. Determine how auto-replies are routed and whether changing the relevant headers preserves DKIM, SPF, and spam-filter compatibility. Done means the behavior and a safe, tested header change are clearly established.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100