|
Size: 9490
Comment:
|
Size: 7911
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma page-filename DEV/versions/3604510 | #pragma page-filename DEV/versions/3604511 |
| Line 6: | Line 6: |
{{{#!wiki caution You might notice some overlap between this list and the one for Mailman 2.2. That's because this page was originally copied from the MM2.2 wish list, and I haven't yet finished reorganizing things since the [[http://mail.python.org/pipermail/mailman-developers/2007-July/019641.html|new roadmap]] was announced. }}} |
|
| Line 17: | Line 13: |
| * '''Python 2.5 or newer will be required.''' | * '''Python 2.5 or newer is required.''' |
| Line 29: | Line 25: |
| * Easy configuration of list styles (this might be a MM3 thing). | * Easy configuration of list styles. |
| Line 33: | Line 29: |
| A web UI improvement project is underway at [[../Summer of Code|summer of code]]: please contribute ideas/thoughts/etc there. | A web UI improvement project was undertaken for the [[../Summer of Code|2006 summer of code]]. Although there were good ideas, we didn't end up with anything usable, so we need to coordinate a new u/i subproject. |
| Line 38: | Line 34: |
| * Get rid of password reminders altogether. Encrypt member passwords and use a password reset feature instead of a reminder. ('''Under way''') | * Get rid of password reminders altogether. Encrypt member passwords and use a password reset feature instead of a reminder. ('''Done''') |
| Line 46: | Line 42: |
| * Possibly integrate [[http://www.spambayes.org|Spambayes]] * Possibly provide a standard SpamAssassin handler * Provide some mechanism whereby the MTA can query Mailman to ask whether the email sender is allowed to send email to the list, so that (when the answer is no) the MTA can reject the email at SMTP time. Currently, Mailman does email rejection after the MTA has accepted email, and all the options available for suspected spam (send an email to the forged sender address, send an email to the list owner, throw the email away) are undesirable. The ideal here would be a daemon that can answer SMTP callout queries, but acceptable would be a small python script which took the sender address and list name as arguments. |
* Possibly integrate [[http://www.spambayes.org|Spambayes]] or [[http://www.spamassassin.org|SpamAssassin]]. * Hook into the LTMP process so that messages can be disposed of as early as possible. Check potential senders and recipients at LTMP time. * Suppress backscatter bounces when [[http://www.opensfp.org|SFP]] headers do not match. |
| Line 67: | Line 63: |
| * Get rid of pickles-as-database, probably settling on something like [[http://www.sqlite.org|SQLite]] as a default database, but also investigate [[http://www.sqlobject.org|SQLObject]] and [[http://www.sqlalchemy.org|SQLAlchemy]] ('''Under way''') * Perhaps also include other database adapters if there are champions to support them. |
* Use a real RDBM on the back end, through a Python-based ORM. ('''Done''') |
| Line 72: | Line 67: |
| * Add a datetime of when the user subscribed to the database, and make this visible. | * Add a datetime of when the user subscribed ('''Done''') |
| Line 79: | Line 74: |
| == Features == * Store additional contact information, like phone numbers, postal addresses, and reference numbers. * Allow members without email addresses. Here's a use case: I'm secretary of a local membership organisation (maybe a political party, or a social club). I need to invite everyone to an annual general meeting, but some people don't have email addresses. With these features, I can use Mailman to send a copy of the message to those that do, and also to produce a list of postal addresses so that I can print labels. Mailman becomes a single tool for organisational membership management. |
Mailman 3.0
This is where I am collecting the feature list and other artifacts for Mailman 3.0 which will be a major upgrade for the project. Many things that people have been wanting for years will be addressed, most notably a unified user database, true virtual domain support, and backing the Mailman data in a real database layer. From a development perspective, we will be adopting a very strict test-driven development model, utilizing modern Python technology and coding styles. The focus will be on providing core Mailman as a library for easy integration into other frameworks and sites, while continuing the tradition of providing a turnkey solution with all the necessary parts, making it even easier to download, install, and go.
There is currently no ETA for Mailman 3, but development is moving quickly. Contributors are welcome and encouraged! Discussions will happen on the mailman-developers mailing list. Anyone can check out and use the current development source branches. The list below is not a commitment of features (unless marked witha Done :)). Add your own as comments and I will move as appropriate into the wish list. You might also want to consider looking at the much more modest Mailman 2.2 branch.
To Do List
Here are things we need to do before MM3 can be released.
- Defend against runaway .bak file restore loops in the Switchboard.
(Potential) feature set
Compatibility and code cleaning
Python 2.5 or newer is required.
Switch to email 4 (Done)
Use Python's standard logging package throughout. (Done)
- Convert the last of the string exceptions in Errors.py to class exceptions
Remove all unnecessary \\_future\\_ statements (Done)
Remove True/False hackery (Done)
Fix unit test suite! (Done)
Eliminate the use of types module as much as possible (Done)
Use the optparse module throughout instead of getopt. (Under way)
Use the subprocess module instead of things like os.popen().
Wart removal
Get rid of the "one list per site with the same name" restriction (cf. FAQ on virtual hosting, Hans Ulrich Niedermann's vhost Branch) (Done)
- Easy configuration of list styles.
Message cleanup
Strip nodup recipients from both the To and Cc headers, and juggle recipient headers so that the list address is always in the To field. This might address the other major complaint against no-reply-to-munging, recipient proliferation.
Web U/I
A web UI improvement project was undertaken for the 2006 summer of code. Although there were good ideas, we didn't end up with anything usable, so we need to coordinate a new u/i subproject.
Privacy
Add an option to allow verified non-members to post to the list. A verified non-member is someone who posts to the list and responds in the affirmative to a confirmation message. A verified member can post in the future (think Gmane).
- Rosters should not be public by default.
Get rid of password reminders altogether. Encrypt member passwords and use a password reset feature instead of a reminder. (Done)
Internationalization
Clean up our Unicode story! All strings should be Unicode internally, with conversion at the boundaries of the system. IWBNI we could get rid of all the catches of UnicodeErrors, however we may have to make changes to things like the email library.
- Switch to a new templating system that lets us share templates across languages, but extract messages for the catalog.
Finish the transition to an externally managed translation system
Switch to $strings (i.e. string.Template instances) for all i18n substitutions. We should be able to mechanically update all existing translations. (Under way)
- Language variants (e.g. en_UK)
Spam defenses
Possibly integrate Spambayes or SpamAssassin.
- Hook into the LTMP process so that messages can be disposed of as early as possible. Check potential senders and recipients at LTMP time.
Suppress backscatter bounces when SFP headers do not match.
Archiving
Note that what we can accomplish here will be based on the availability of an Archiving Champion.
- Reconsider using a 3rd-party archiver
Perhaps URLs to messages should be based on message-ids instead of message numbers so that regenerating archives can't break links. This must include backward compatible links
- Ditch direct access and vend all archive messages through CGI so that we can do address obfuscation, and message deletion, etc. on the fly (with caching of course, but have to worry about web crawlers).
- Allow for admins to remove or edit messages through the web.
- Move archive threads into another list?
Put archives in the list/mylist directory.
- Add a search option
Make archives default template look and feel similar to Web UI (whatever it looks like after the Summer of Code project is done)
- Make archive templatable (at least by changing CSS) so they can match people's existing site look-and-feel
- MUAs usually make URLs clickable. An new Archive could be used when posts are distributed, in the footer, so that each message has a link to the whole thread in the Archive.
- Present all messages in a thread at once, and offer plaintext download of the whole thread
- Put messages into a database and/or move away from mbox as the canonical storage format.
Operational/Performance/Administration
- Improve admin statistics gather (# of posts sent, # bounced, # of domains accessed, which lists are quiet and which are busy) and make these available via the web interface.
Use a real RDBM on the back end, through a Python-based ORM. (Done)
- Caps for list member count and outgoing messages per time slice.
- Better feedback to users who have bounced (e.g. put a link to their last bounced message on their member page).
- The 'digest option' needs to be improved to delete 'double messages'
Add a datetime of when the user subscribed (Done)
Provide a better list-data export and import mechanism via XML. Possibly allow for data export via the web.
For Postfix, switch to separate domains, non-UNIX accounts virtual domains and maildir delivery by default. Delivery mechanics for other MTAs may or may not change.
- Partition queue directories into hashed subdirectories so that all queue files do not live in the same directory (which increases contention on the directory inodes and reduces overall performance).
- Fix the bounce probe problem, and make bounce processing more efficient. Right now, it sucks.
- Discard messages that have been in the bounces or shunt queues for a long time.
- Include message headers in discard notifications - currently it isn't always possible to tell who sent a message that's been discarded, which makes it a bit pointless sending a notification. It would be nice to include brief headers in the first message part.