next message in archive
no next message in thread
previous message in archive
Index of Subjects
Last night I got the (majordomo) mailing list update function runing on
Chebucto...
Currently our majordomo is using (multiple) zmailer aliases files (see
below) to manage addresses for list-owner and (majordomo) approvals...
and the update function now is able to modify these as necessary.
An added benefit has been the ability to have more then one list-owner.
----
This was one of the few remaining obstacles to moving to an (almost)
standard version of zmailer for the distribution. (we're still making a
couple of patches...
----
Over the short while (days) we expect to be able to update the cvs with a
current version of zmailer (and the associated majoromo management
scripts...)
david potter
Majordomo aliasing....
-------------------------------
Chebucto is currently using three aliase files:
- aliases
- md-owner
- md-other
...that are combined when zmailer newaliases builds the new database.
md-owner - includes
[listname]-owner: user ("user, user" or user@address etc..)
md-other - includes
[listname]-approval: [listname]-owner
[listname]-mml-owner: [listname]-owner
[listname]-owner-owner: [listname]-owner
-----
IP create and mailing list creation scripts update these aliase files and
the mailing list update script modifies md-owner.
zmailer/bin/newaliases is called after all modifications.
next message in archive
no next message in thread
previous message in archive
Index of Subjects