forwardemail / forwardemail/forwardemail.net
[feat] Support Protected Headers
Open
enhancement
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 203
- PR merge metrics
- No merged PRs in 30d
Description
Three solutions:
1. Prefered: RFC 9788 (Header Protection for Cryptographically Protected Email)
2. Striping and placing in mail body, while modifying Subject to empty or generic one.
3. At least deleting Subject without manual Seive rules before forwarding.
Contributor guide
Research direction
No files, tests, or entry points are named. Start by clarifying whether RFC 9788, placing headers in the body, or deleting the Subject is intended, then define the protected-header behavior and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100