Mailman, the GNU Mailing List Manager
The other goal for the next release is to include real user databases. A user should be able to have one Mailman login for all lists of which they are members at a site. This login should contain a list of all addresses to which messages can potentially be delivered and should allow the user to select which mailing list delivers to which address. Additionally, each user would need to remember only one password to change their delivery options.
Currently, each Mailman list maintains its own list of member addresses. This makes the data store relatively easy to implement and recipient calculation fast, but it can be a real pain for users who are subscribed to many lists at a particular site. For list administrators who own multiple lists, it's even worse. For this reason, we want to move toward having a real database of users and administrators in the back end, using caching or other techniques to make membership calculation perform acceptably. One of the core Mailman maintainers has an implementation of this that he's currently testing, and it is expected to be integrated some time soon. This change may be significant enough to call the next release of Mailman version 2.0.
Barry Warsaw (email@example.com) is Project Lead for Software Development with the MEMS Exchange at CNRI. He is the current primary maintainer of Mailman and JPython, the 100% Pure Java implementation of Python. Barry has used and contributed to Python since 1994. He has also written and maintained numerous other smaller open-source projects over the last 15 years, including CC Mode for Emacs.
- How to Calculate Flash Storage TCO
- Non-Linux FOSS: Don't Drink the Apple Kool-Aid; Brew Your Own!
- Two Ways GDPR Will Change Your Data Storage Solution
- Readers' Choice Awards
- Returning Values from Bash Functions
- Preseeding Full Disk Encryption
- Hodge Podge
- Three EU Industries That Need HPC Now
- GRUB Boot from ISO
- HOSTING Monitoring Insights