Usenet / mailing list gateway not working since migration to Mailman 3
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- documentation, infrastructure
Research direction
Start by comparing the bidirectional gateway behavior described for comp.lang.python and python-list with the Mailman 3 archive linked in the issue. Check the community/lists/ page and its old archive link, then verify that messages move in both directions. Done means the gateway works again and the page points to the new archive URL.
Written by the indexing model from the issue text.
Description
The comp.lang.python usenet newsgroup has been very quiet for the last couple of months. Taking a look at the mailing list archive, it looks like recent messages aren't being transferred in either direction - recent newsgroup posts don't appear on the mailing list archive, and recent messages to the mailing list don't seem to be reaching the newsgroup.
The description of the newsgroup and mailing list at https://www.python.org/community/lists/ still says that there's supposed to be a bidirectional gateway between the two. The link there for the "python.org archive of python-list" leads to an archive that stops in May 2025, with an explanation that "this list has been migrated to Mailman 3" and link to the new archive. That appears to coincide with the gateway stopping.
Aside from fixing the gateway, the link to the mailing list archive from https://www.python.org/community/lists/ should probably be updated to link to the new archive at https://mail.python.org/archives/list/python-list@python.org/latest.
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 700
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 14
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.
More from python/pythondotorg
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
python/pythondotorg#3137 · 2 comments ·
-
app/pages bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
python/pythondotorg#2677 · 3 comments ·
-
backend easy
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
python/pythondotorg#2453 · 8 comments ·
-
bug good-first-issue
Difficulty 4/5 3-5 days Newbie friendliness 30/100
python/pythondotorg#3125 · 1 comment ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 74/100
python/pythondotorg#3094 · 5 comments ·
All issues in python/pythondotorg
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
anthropics/skills#1811 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
speaches-ai/speaches#678 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
datalayer/mcp-compose#42 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conda-forge/spacy-feedstock#177 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
UKGovernmentBEIS/inspect_evals#2523 ·