[求助]Mailman+podtfix virtual domain配置问题

aborigen

http://www.list.org/devs.html

Future plans
Now that Mailman 2.1 has been released, I want to start thinking about what will be in Mailman 3.0. I intend to use the wiki for most design artifacts, and the mailman-developers mailing list for most discussions. The items that are high on my list (which is by no means complete or definitive) include:
Consolidated user database -- A user should have just one account for every mailing list they are members of at a site, and they should be able to manage all their options through this account. It should be possible to integrate these databases with a site's existing user management system to reduce duplication of data and effort.

Unified template system -- Mailman has a somewhat fractured and inconvenient templating system, using both a homegrown HTML object model in Python and coarse templates filled in with data at rendering time. It can be near impossible to change the look and feel of the administration pages, and a small change to the u/i of other pages requires updates in all supported languages. I want to use a templating system like ZPT or Quixote. Actually, I plan to generalize the web interface so that many different templating systems could be used, although we'll pick one to ship by default.

A Real Database -- Mailman uses an inefficient persistency system based on Python pickles, and every mailing list has its own pickled state. This has several disadvantages, including poor scalability, difficulty in doing cross-mailing list operations, and the virtual host limitation on list names. Mailman 3.0 will use a real database, perhaps based on ZODB or BerkeleyDB. Again, the goal is to generalize the interface to the backend database so that others can be used, but choose one and ship it by default.

Component Architecture -- Zope3's component architecture provides some very nice organizational tools and software development methodologies. We'll be adopting many of these for Mailman 3.0, which will allow us to do the kinds of templating and database generalization described above.

aborigen

http://www.list.org/todo.html

Portability & architecture
Use a real transactional database for all information, and allow various bits of information to come from different sources (a relational database, ZODB, LDAP, etc)
Member profiles
Allow lists of the same name in two different virtual domains
Should be able to gather statistics, such as deliveries/day, performance, number of subscribers over time, etc.
Implement something like Roundup's nosy lists, maybe even integrate with Roundup.
Split Mailman into libraries so, e.g. the delivery part could be used by other projects.

aborigen

还有很长的路要走啊~~~

peijun.jiang

[quote]原帖由 "aborigen"]还有很长的路要走啊~~~[/quote 发表：
  

继续努力，从精神上支持你！

aborigen

原帖由 "peijun.jiang" 发表：


继续努力，从精神上支持你！

   


来点实际的好不好?快快学习python,参与mailman开发~~~