Clarification: 1.3.11 SMTP
Open
Nobody has claimed this yet.
4a) Waiting for another
V1 (prev V5)
- Dominant language
- HTML
- Stars
- 3.6k
- Forks
- 831
- Avg merge
- 7h 55m
- Merged PRs (30d)
- 4
Description
1.3.10 Verify that the application sanitizes user input before passing to mail
systems to protect against SMTP or IMAP injection.
- It is good to add in the requirement, use strict validation and language-native email APIs (like JavaMail or Python’s email module) instead of relying on sanitization.
- Is it good to add CRLF Injection name?
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 reviewing requirement 1.3.10 and the proposed wording about strict validation, language-native email APIs, and CRLF injection. Read the 30-comment discussion to understand the unresolved terminology and scope. Done means the requirement language and whether to name CRLF injection are agreed and documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, python
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100