The datatracker should honor "active" or not email everywhere.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by auditing every code path that sends email, including paths that accept bare addresses from outside sources, and trace how recipient activity is checked. Done means inactive known addresses are replaced with an appropriate active address or not pursued when context requires, consistently across all sending paths.
Written by the indexing model from the issue text.
Description
Right now, the codebase is not consistent in checking the "active" bit when sending email.
Instead, anytime the datatracker sends mail, it should look to see if any address it's about to send to is known to be non-active and use a better address for the person instead. Pay attention to context - there may be cases where the right thing to do is not pursue the address further instead of looking for a better one.
Note that some parts of the code take bare addresses from outside sources and send mail to them (such as when submitting drafts). Those should be amended to look to see if the addresses are known and active.
Aggregated with agent assistance on 2026-08-18
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 853
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 45
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.
More from ietf-tools/datatracker
-
bug under_review
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ietf-tools/datatracker#11683 · 2 comments ·
-
accepted bug component: doc/ component: group/ major
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ietf-tools/datatracker#11655 · 1 comment ·
-
component: community/ enhancement medium
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ietf-tools/datatracker#11637 ·
-
accepted component: group/ enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ietf-tools/datatracker#11631 · 1 comment ·
-
component: group/ medium
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
ietf-tools/datatracker#11581 ·
All issues in ietf-tools/datatracker
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100