diff options
| -rw-r--r-- | BUGS | 9 | ||||
| -rw-r--r-- | README | 45 |
2 files changed, 35 insertions, 19 deletions
@@ -1,3 +1,5 @@ +Send bug reports to mailman-developers@python.org + Known bugs: - There seems to be a problem building the C wrappers on FreeBSD @@ -6,3 +8,10 @@ Known bugs: anything more about the causes, and there is some suspicion that the problem is unrelated to Mailman. Using gmake to build Mailman appears to solve the problem. + + + +Local Variables: +mode: indented-text +indent-tabs-mode: nil +End: @@ -2,8 +2,8 @@ Mailman - The GNU Mailing List Management System Copyright (C) 1998 by the Free Software Foundation, Inc. 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA - Background - ========== + Background + ========== This is Mailman, a mailing list management system written mostly in Python. Mailman was originally developed by John Viega. Subsequent development (through version 1.0b3) was by Ken Manheimer. Currently, @@ -27,7 +27,7 @@ See file DONE for info on changes since v. 0.9 Features: o Most standard mailing list features, including: - moderation, mail based commands, digests, etc... + moderation, mail based commands, digests, etc... o An extensive Web interface customizable on a per-list basis. o Web based list administration interface for *all* admin-type tasks. o Automatic Web based hypermail-style archives (using pipermail or @@ -45,11 +45,11 @@ Features: o Multiple list owners and moderators are possible o Optional MIME-compliant digests o Nice about which machine you subscribed from if you're from the - right domain. + right domain. - Using Mailman - ============= + Using Mailman + ============= Requirements: [XXX: This needs to be reviewed] @@ -84,19 +84,19 @@ How to add a new user option You'll need to do some of these things and not others. - 1) Add a flag to mm_defaults.py, and mm_cfg.py.dist if it's - likely to require a custom value for each site. - 2) Add an entry to mm_html GetStandardReplacements name - & mapping, to enable referring to the value from mailman html. - 3) Add replacements lines to the cgi/options and cgi/listinfo - scripts, to hook the mailman html up with the option. - 4) For user-specific options, make SetUserOption calls in - & cgi/handle_opts. - 5) For user-specific options, add to 2 data structs at top of - & mm_mailcmd. - 6) For user-specific options, add description to mm_mailcmd help - 7) Update templates if the options have replacements - 8) Use your option wherever appropriate... + 1) Add a flag to mm_defaults.py, and mm_cfg.py.dist if it's + likely to require a custom value for each site. + 2) Add an entry to mm_html GetStandardReplacements name + & mapping, to enable referring to the value from mailman html. + 3) Add replacements lines to the cgi/options and cgi/listinfo + scripts, to hook the mailman html up with the option. + 4) For user-specific options, make SetUserOption calls in + & cgi/handle_opts. + 5) For user-specific options, add to 2 data structs at top of + & mm_mailcmd. + 6) For user-specific options, add description to mm_mailcmd help + 7) Update templates if the options have replacements + 8) Use your option wherever appropriate... Interactive python sessions with maillists @@ -155,3 +155,10 @@ Interactive python sessions with maillists Beware that "list surgery" can be easily used to foul up your list data structures - so be careful, and confident of what you're done *before* any list .Save()'s are applied... + + + +Local Variables: +mode: indented-text +indent-tabs-mode: nil +End: |