The datatracker should honor "active" or not email everywhere.

Open
#6,281 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

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

accepted component: Datatracker: Email sending enhancement

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ietf-tools/datatracker

All issues in ietf-tools/datatracker

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.