??changed:
-where Mailman is installed (though, some tasks like changing the
-password for a list can be done via the web interface and the
-site-wide admin password).
-
-See MailSystem for architecture details.
where Mailman is installed, while others, such as changing the
password for a list, can be done via the web interface and the
site-wide admin mailman password. See MailSystem for architecture details.
??changed:
-user `list'. You will be greeted with the bash prompt::
user 'list'. You will be greeted with the bash prompt::
??changed:
-Project admins can now create their own mailing lists if they are
-named PROJECTNAME-*. This is done through the normal
Project admins can create their own mailing lists if they are
named PROJECTNAME-*, or {bug,info,help}-PROJECTNAME. This is done through the
normal
??changed:
-(that day we'll most probably also allow several mailing list naming
conventions for a project group type :))
-
-If the project admin agrees, another option is to have the list
-use PROJECTNAME-* and thus be created through the web interface,
-and then create an alias in fencepost:/com/mailer/aliases. This
-is recommended for the standard bug-* convention for GNU packages.
-(Have the project create *-bugs or *-discuss, then make bug-*
-an alias.)
Simple aliases, as opposed to lists, can be created in
fp.gnu.org:/com/mailer/aliases.
--
forwarded from
https://savannah.gnu.org/maintenance/listserver#msg20090316180357+0...@https://savannah.gnu.org/maintenance
_______________________________________________
Savannah-cvs mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/savannah-cvs
