gforge-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gforge-devel] [ gforge-Bugs-454 ] Mailing list Scripts should use newli


From: noreply
Subject: [Gforge-devel] [ gforge-Bugs-454 ] Mailing list Scripts should use newlist command instead of directly modifying alias file
Date: Mon, 21 Jul 2003 22:12:58 -0500

Bugs item #454, was opened at 2003-07-21 20:12
You can respond by visiting: 
http://gforge.org/tracker/?func=detail&atid=105&aid=454&group_id=1

Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Gavin Mogan (halkeye)
Assigned to: Nobody (None)
Summary: Mailing list Scripts should use newlist command instead of directly 
modifying alias file

Initial Comment:
All installations of mailman comes with a command
called newlist which creates a list.

This file should be used for the cronjobs instead of
directly modifying the alias list.

This would help people like me who have used the
dynamic method of setting up postfix as to not need to
edit the alias files all the time.
See: 
http://www.gurulabs.com/files/postfix-to-mailman-2.1.py
and http://listes.rezo.net/how.php

I'll try to get around to making a patch if i can ever
get php command line interface to run scripts.

I will gladly write a perl script todo this if the need
 arrises.

-----

address@hidden:/usr/lib/mailman# bin/newlist  --help
Create a new, unpopulated mailing list.

Usage: bin/newlist [options] [listname [listadmin-addr
[admin-password]]]

Options:

    -l language
    --language language
        Make the list's preferred language `language',
which must be a two
        letter language code.

    -q/--quiet
        Normally the administrator is notified by email
(after a prompt) that
        their list has been created.  This option
suppresses the prompt and
        notification.

    -h/--help
        Print this help text and exit.

You can specify as many of the arguments as you want on
the command line:
you will be prompted for the missing ones.

Every Mailman list has two parameters which define the
default host name for
outgoing email, and the default URL for all web
interfaces.  When you
configured Mailman, certain defaults were calculated,
but if you are running
multiple virtual Mailman sites, then the defaults may
not be appropriate for
the list you are creating.

You can specify the domain to create your new list in
by spelling the listname
like so:

    address@hidden

where `www.mydom.ain' should be the base hostname for
the URL to this virtual
hosts's lists.  E.g. with is setting people will view
the general list
overviews at http://www.mydom.ain/mailman/listinfo. 
Also, www.mydom.ain
should be a key in the VIRTUAL_HOSTS mapping in
mm_cfg.py/Defaults.py.  It
will be looked up to give the email hostname.  If this
can't be found, then
www.mydom.ain will be used for both the web interface
and the email
interface.

If you spell the list name as just `mylist', then the
email hostname will be
taken from DEFAULT_EMAIL_HOST and the url will be taken
from DEFAULT_URL (as
defined in your Defaults.py file or overridden by
settings in mm_cfg.py).

Note that listnames are forced to lowercase.

The list admin address need to be a fully-qualified
address, like
address@hidden, not just owner.


----------------------------------------------------------------------

You can respond by visiting: 
http://gforge.org/tracker/?func=detail&atid=105&aid=454&group_id=1




reply via email to

[Prev in Thread] Current Thread [Next in Thread]