![](https://secure.gravatar.com/avatar/e1144b7d14897d039827ecff756163d8.jpg?s=120&d=mm&r=g)
Wow! I'm impressed. Once past the initial hurdle of the vsnprintf problem and Solaris 2.5, I had mailman installed and working in less that an hour. Beautiful!
In case this hasn't been discussed already, I have a suggestion for handling the mailman aliases.
The INSTALL file says:
- Add aliases for `mailman' and `owner-mailman' to the system's
mail alias database. These aliases should point to whoever is
ultimately responsible for the Mailman installation. Here are
instructions for those running sendmail:
1. su to root.
2. Assuming your email is fred@flintstone.com, add the following
lines to the file /etc/aliases:
mailman: fred@flintstone.com
mailman-owner: mailman
3. Some versions of sendmail require you to run the program
'newaliases' explicitly.
I did this a little differently:
- add to /etc/mail/sendmail.cf
O AliasFile=/home/mailman/aliases
- create the /home/mailman/aliases dbm files cd /home/mailman
- edit aliases and add mailman and mailman-owner alias entries as above touch aliases.dir aliases.pag chown root aliases* chgrp mailman aliases*
- run newaliases and restart sendmail
When adding a new list:
/home/mailman/bin/newlist list-name list-admin-address admin-password 1 >> /home/mailman/aliases
then you just have to edit the aliases file to remove the extra junk output by newlist (but this could be suppressed when the immediate flag is used) and run newaliases.
--
Todd Pfaff \ Email: pfaff@mcmaster.ca
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University
Hamilton, Ontario, Canada L8S 4M1 \
![](https://secure.gravatar.com/avatar/e1144b7d14897d039827ecff756163d8.jpg?s=120&d=mm&r=g)
On Wed, 28 Jul 1999, Ron Jarrell wrote:
Why? I'm not. I used to do the same thing with majordomo and I never dedicated the machine to majordomo.
I said "add to sendmail.cf" not replace. The sendmail.cf can include multiple alias files.
--
Todd Pfaff \ Email: pfaff@mcmaster.ca
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University
Hamilton, Ontario, Canada L8S 4M1 \
![](https://secure.gravatar.com/avatar/ebb666325562d3790b5d78feae4b59c1.jpg?s=120&d=mm&r=g)
Does anyone know the correct configuration to make an "umbrella" list work? I have two lists, diva-interest and diva-notify, and diva-interest has diva-notify as one of its members.
The configuration settings for diva-notify are:
Must posts be approved by an admin: No Restrict posting privileges to list members: Yes Addresses accepted without implicit approval requirements:
diva-interest-admin@gigascale.EECS.Berkeley.EDU diva-interest@gigascale.EECS.Berkeley.EDU
However, posts sent to diva-interest@gigascale.eecs.berkeley.edu are held for approval as follows (from the admindb page):
Post held because: Only approved posters may post without moderator approval.
I think I've tried about every combination of options... Help!
BTW, my Defaults.py says
USE_ENVELOPE_SENDER = 0
JohnR
![](https://secure.gravatar.com/avatar/77347749a4199b9e6b142bb6977d5c73.jpg?s=120&d=mm&r=g)
I've not upgraded to the absolute latest, but I'm not too far behind.
We have a number of "announcement" lists.
Am I missing a way to tell Mailman that this is an announcement list? What I expect is that the listinfo screen would stop saying "To post a message to all the list members, send email to listaddress@mydomain.dom" if it is restricted. Yeah, we say in the description that it is read-only, and that only certain people can post to it, but that instruction is still there just below it.
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"MC" == Merrill Cook <mcook@unidial.com> writes:
MC> Am I missing a way to tell Mailman that this is an
MC> announcement list? What I expect is that the listinfo screen
MC> would stop saying "To post a message to all the list members,
MC> send email to listaddress@mydomain.dom" if it is
MC> restricted. Yeah, we say in the description that it is
MC> read-only, and that only certain people can post to it, but
MC> that instruction is still there just below it.
Sorry, the best you can do right now is to edit the general listinfo HTML page to comment out this text.
-Barry
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"TP" == Todd Pfaff <pfaff@edge.cis.mcmaster.ca> writes:
TP> Wow! I'm impressed. Once past the initial hurdle of the
TP> vsnprintf problem and Solaris 2.5, I had mailman installed and
TP> working in less that an hour. Beautiful!
Yay!
TP> In case this hasn't been discussed already, I have a
TP> suggestion for handling the mailman aliases.
This approach might allow us (at least for sendmail) to easily add new lists via the Web. You'd only have to hack ~mailman/aliases -- which you'd presumably wouldn't have to be root to do.
-Barry
![](https://secure.gravatar.com/avatar/e1144b7d14897d039827ecff756163d8.jpg?s=120&d=mm&r=g)
On Thu, 29 Jul 1999, Barry A. Warsaw wrote:
You have to set the ownership and permissions of the ~mailman/aliases* files carefully or sendmail complains about an unsafe dbm file. I've experimented a bit and found the following works fine:
# ls -alg /home/mailman/aliases* -rw-rw-r-- 1 root mailman 1869 Jul 29 23:43 /home/mailman/aliases -rw-r--r-- 1 root mailman 4096 Jul 29 23:44 /home/mailman/aliases.dir -rw-r--r-- 1 root mailman 2048 Jul 29 23:44 /home/mailman/aliases.pag
--
Todd Pfaff \ Email: pfaff@mcmaster.ca
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University
Hamilton, Ontario, Canada L8S 4M1 \
![](https://secure.gravatar.com/avatar/607d7afcd8e5d5c725bfd000d8f9edee.jpg?s=120&d=mm&r=g)
I have not yet gotten for enough to determine whether Mailman can read the NIS map aliases. I wasn't worried about it because I thought it a normal enough thing, but these latest questions about aliases makes me wonder. Is NIS:mail.aliases workable?
thanks, jeff
![](https://secure.gravatar.com/avatar/949a830d79baf47b5006b5dff4c86bd7.jpg?s=120&d=mm&r=g)
Is there a FAQ available that deals specifically with how to setup a MailMan list with multiple moderators? I'm leery of giving the admin password to all the moderators.
Ken Kyler
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"JS" == Jeff Schneiter <jschneit@Adobe.COM> writes:
JS> I have not yet gotten for enough to determine whether Mailman
JS> can read the NIS map aliases. I wasn't worried about it
JS> because I thought it a normal enough thing, but these latest
JS> questions about aliases makes me wonder. Is NIS:mail.aliases
JS> workable?
I think this is outside the scope of Mailman. You just need to be sure that the wrapper gets called as a filter program.
-Barry
![](https://secure.gravatar.com/avatar/e1144b7d14897d039827ecff756163d8.jpg?s=120&d=mm&r=g)
On Wed, 28 Jul 1999, Ron Jarrell wrote:
Why? I'm not. I used to do the same thing with majordomo and I never dedicated the machine to majordomo.
I said "add to sendmail.cf" not replace. The sendmail.cf can include multiple alias files.
--
Todd Pfaff \ Email: pfaff@mcmaster.ca
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University
Hamilton, Ontario, Canada L8S 4M1 \
![](https://secure.gravatar.com/avatar/ebb666325562d3790b5d78feae4b59c1.jpg?s=120&d=mm&r=g)
Does anyone know the correct configuration to make an "umbrella" list work? I have two lists, diva-interest and diva-notify, and diva-interest has diva-notify as one of its members.
The configuration settings for diva-notify are:
Must posts be approved by an admin: No Restrict posting privileges to list members: Yes Addresses accepted without implicit approval requirements:
diva-interest-admin@gigascale.EECS.Berkeley.EDU diva-interest@gigascale.EECS.Berkeley.EDU
However, posts sent to diva-interest@gigascale.eecs.berkeley.edu are held for approval as follows (from the admindb page):
Post held because: Only approved posters may post without moderator approval.
I think I've tried about every combination of options... Help!
BTW, my Defaults.py says
USE_ENVELOPE_SENDER = 0
JohnR
![](https://secure.gravatar.com/avatar/77347749a4199b9e6b142bb6977d5c73.jpg?s=120&d=mm&r=g)
I've not upgraded to the absolute latest, but I'm not too far behind.
We have a number of "announcement" lists.
Am I missing a way to tell Mailman that this is an announcement list? What I expect is that the listinfo screen would stop saying "To post a message to all the list members, send email to listaddress@mydomain.dom" if it is restricted. Yeah, we say in the description that it is read-only, and that only certain people can post to it, but that instruction is still there just below it.
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"MC" == Merrill Cook <mcook@unidial.com> writes:
MC> Am I missing a way to tell Mailman that this is an
MC> announcement list? What I expect is that the listinfo screen
MC> would stop saying "To post a message to all the list members,
MC> send email to listaddress@mydomain.dom" if it is
MC> restricted. Yeah, we say in the description that it is
MC> read-only, and that only certain people can post to it, but
MC> that instruction is still there just below it.
Sorry, the best you can do right now is to edit the general listinfo HTML page to comment out this text.
-Barry
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"TP" == Todd Pfaff <pfaff@edge.cis.mcmaster.ca> writes:
TP> Wow! I'm impressed. Once past the initial hurdle of the
TP> vsnprintf problem and Solaris 2.5, I had mailman installed and
TP> working in less that an hour. Beautiful!
Yay!
TP> In case this hasn't been discussed already, I have a
TP> suggestion for handling the mailman aliases.
This approach might allow us (at least for sendmail) to easily add new lists via the Web. You'd only have to hack ~mailman/aliases -- which you'd presumably wouldn't have to be root to do.
-Barry
![](https://secure.gravatar.com/avatar/e1144b7d14897d039827ecff756163d8.jpg?s=120&d=mm&r=g)
On Thu, 29 Jul 1999, Barry A. Warsaw wrote:
You have to set the ownership and permissions of the ~mailman/aliases* files carefully or sendmail complains about an unsafe dbm file. I've experimented a bit and found the following works fine:
# ls -alg /home/mailman/aliases* -rw-rw-r-- 1 root mailman 1869 Jul 29 23:43 /home/mailman/aliases -rw-r--r-- 1 root mailman 4096 Jul 29 23:44 /home/mailman/aliases.dir -rw-r--r-- 1 root mailman 2048 Jul 29 23:44 /home/mailman/aliases.pag
--
Todd Pfaff \ Email: pfaff@mcmaster.ca
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University
Hamilton, Ontario, Canada L8S 4M1 \
![](https://secure.gravatar.com/avatar/607d7afcd8e5d5c725bfd000d8f9edee.jpg?s=120&d=mm&r=g)
I have not yet gotten for enough to determine whether Mailman can read the NIS map aliases. I wasn't worried about it because I thought it a normal enough thing, but these latest questions about aliases makes me wonder. Is NIS:mail.aliases workable?
thanks, jeff
![](https://secure.gravatar.com/avatar/949a830d79baf47b5006b5dff4c86bd7.jpg?s=120&d=mm&r=g)
Is there a FAQ available that deals specifically with how to setup a MailMan list with multiple moderators? I'm leery of giving the admin password to all the moderators.
Ken Kyler
![](https://secure.gravatar.com/avatar/ab1c33fc0fd591a0ea174155233a6a51.jpg?s=120&d=mm&r=g)
"JS" == Jeff Schneiter <jschneit@Adobe.COM> writes:
JS> I have not yet gotten for enough to determine whether Mailman
JS> can read the NIS map aliases. I wasn't worried about it
JS> because I thought it a normal enough thing, but these latest
JS> questions about aliases makes me wonder. Is NIS:mail.aliases
JS> workable?
I think this is outside the scope of Mailman. You just need to be sure that the wrapper gets called as a filter program.
-Barry
participants (9)
-
Barry A. Warsaw
-
Christopher Lindsey
-
Jeff Schneiter
-
John Reekie
-
John Viega
-
Ken Kyler
-
Merrill Cook
-
Ron Jarrell
-
Todd Pfaff