max-mapper / max-mapper/haraka-couchdb
Use recipient as "db" not headers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 49
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Shouldn't you use connection.transaction.rcpt_to as the recipients, not the headers you're looking at? And you probably need to loop through them and store one document for each.
Each item in the array is an Address object, which has .user and .host properties already.
Contributor guide
No contributing guide indexed for this repository
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 tracing where connection.transaction.rcpt_to and the message headers are used to create documents. Check the Address objects' user and host properties, then verify the handling for multiple recipients. Done means one document is stored for each recipient from rcpt_to rather than from the headers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100