
GNU Mailman manages your mailing lists.
Showing 5 of 8 projects. Click any project card for scope, mentors, and proposal studio.
Mentors: Student: Navya Khanna
Mailman 3 has no way to back up or restore a single mailing list. If a list is accidentally deleted or a database migration goes wrong, there is no recovery path. This project builds one: two CLI commands: mailman backup and mailman restore, backed by a schema-validated JSON export format. The backup captures all list state: 85 config fields, member roster across all three roles, header-match rules, aliases, bans, and archiver states. Restore validates the file against a JSON Schema before touching the database, guards against missing domains, preserves verified_on exactly, and uses an is_subscribed() pre-check to avoid SQLAlchemy session poisoning. The operation is silent so no welcome or verification emails are triggered.
Mentors: Student: a-khushal
This project implements the domain owner role in Postorius. Right now, Mailman 3 has site admins, list owners, and list moderators, but domain administration is not fully complete. This project will allow domain owners to create mailing lists only in domains they own, use list-owner features for lists in those domains, and edit settings for their domains. The work involves updating Postorius auth helpers, reusing existing decorators and mixins, updating list creation and domain edit views, making UI changes, and adding tests. Expected result: working support for domain owners to manage lists and domains they own, along with proper test coverage.
Mentors: Student: Archie Singh
For broadcasting messages, mailing lists are essential but high traffic lists frequently fill the inboxes with replies to threads of a particular topic that subscribers have no interest in. This project introduces Dynamic Sublists into the GNU Mailman 3 suite. This is an ideal feature for user-support community groups or for issue tracking where topics of interests/specific tasks diverge from the main discussion thread. The earlier rigid broadcast model is transformed into an opt-in thread model, ensuring only the root email of a new topic is broadcast to the main mailing list, after which the next round of replies will be routed strictly to a child list, delivering the mail to users who have explicitly opted in. Sublists are treated as dynamically made child MailingList objects linked via a parent_id. This project requires implementation across Mailman 3 Core, extending the SQLAlchemy IMailingList schema, implementing inheritance, building the email command workflow (-new to fork threads and standard -join/-leave aliases), and adding an admin specific toggle for Postorius.
Mentors: Student: Amitxtech
The current Postorius subscriber management page has limited member visibility, no filtering options, and requires full page navigation to edit preferences. This proposal adds a Display Name column with sortable headers, filter dropdowns for delivery status/mode/moderation action with bookmarkable URL params, an expandable inline row for quick preference editing without page navigation, and private list visibility for subscribers with lock icon indicators.
Mentors: Student: berserker1
<p>This proposal’s main goal is to add a concrete and fully functional form of implementation/procedure for processing of various messages and taking the required action. These messages are in turn extracted from the bounce messages which in turn are received to the sender when the email is not received by the receiver.</p>