Mailman not automatically updating its aliases file
Hi, I was recently tasked with setting up a new mailman server.
We installed mm2.1.9 via yum on a RHEL5.3 server with postfix installed.
varprefix=/var/lib/mailman and prefix =/usr/lib/mailman.
This is what I have for custom lines in my mm_cfg.py:
DEFAULT_EMAIL_HOST = 'mm server name' DEFAULT_URL_HOST = 'mm server name'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
MTA = 'Postfix' VIRTUAL_HOST_OVERVIEW = 0 OWNERS_CAN_ENABLE_PERSONALIZATION = 1
My problem is that whenever I use the newlist command and I create a list, it doesnt automatically update the aliases file. According to the install documentation on the mailman website, I only had to do a few things including adding MTA='Postfix', etc. Are there any other settings that I need to check on in order to make sure it is working?
Thanks for any replies.
Mark Ratcliff wrote:
We installed mm2.1.9 via yum on a RHEL5.3 server with postfix installed.
varprefix=/var/lib/mailman and prefix =/usr/lib/mailman.
This is what I have for custom lines in my mm_cfg.py:
DEFAULT_EMAIL_HOST = 'mm server name' DEFAULT_URL_HOST = 'mm server name'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
MTA = 'Postfix' VIRTUAL_HOST_OVERVIEW = 0 OWNERS_CAN_ENABLE_PERSONALIZATION = 1
My problem is that whenever I use the newlist command and I create a list, it doesnt automatically update the aliases file. According to the install documentation on the mailman website, I only had to do a few things including adding MTA='Postfix', etc. Are there any other settings that I need to check on in order to make sure it is working?
Does newlist report any error?
Are /var/lib/mailman/data/aliases* not being updated or is the problem that Postfix doesn't use those aliases?
See http://www.list.org/mailman-install/node13.html.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Newlist doesn't report any errors. As far as I can tell postfix sees the /var/lib/mailman/data/aliases.db just fine but when I add a new list the newlist command does not write the new aliases to the aliases file nor does it update the aliases.db file.
Ownership is set to mailman:mailman with group read/write perms on the aliases file ( I had to create this file manually ).
Could this just be a bug in the RHEL5 package? I can work around this by just manually updating aliases, however I'd like to try to find out if maybe I did something wrong.
-----Original Message----- From: Mark Sapiro [mailto:mark@msapiro.net] Sent: Friday, August 21, 2009 8:07 PM To: Mark Ratcliff; mailman-users@python.org Subject: Re: [Mailman-Users] Mailman not automatically updating its aliases file
Mark Ratcliff wrote:
We installed mm2.1.9 via yum on a RHEL5.3 server with postfix
installed.
varprefix=/var/lib/mailman and prefix =/usr/lib/mailman.
This is what I have for custom lines in my mm_cfg.py:
DEFAULT_EMAIL_HOST = 'mm server name' DEFAULT_URL_HOST = 'mm server name'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
MTA = 'Postfix' VIRTUAL_HOST_OVERVIEW = 0 OWNERS_CAN_ENABLE_PERSONALIZATION = 1
My problem is that whenever I use the newlist command and I create a list, it doesnt automatically update the aliases file. According to the
install documentation on the mailman website, I only had to do a few things including adding MTA='Postfix', etc. Are there any other settings that I need to check on in order to make sure it is working?
Does newlist report any error?
Are /var/lib/mailman/data/aliases* not being updated or is the problem that Postfix doesn't use those aliases?
See http://www.list.org/mailman-install/node13.html.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark Ratcliff wrote:
Newlist doesn't report any errors.
If newlist doesn't report an error, and you have as you said MTA = 'Postfix' in mm_cfg.py, then newlist must be updating some aliases file.
As far as I can tell postfix sees the /var/lib/mailman/data/aliases.db just fine but when I add a new list the newlist command does not write the new aliases to the aliases file nor does it update the aliases.db file.
See the FAQ at http://wiki.list.org/x/KYCB. It claims the aliases are at /etc/mailman/aliases in recent RedHat. I think that this is just a symlink to /var/lib/mailman/data/aliases or vice versa, but it's worth a look.
Ownership is set to mailman:mailman with group read/write perms on the aliases file ( I had to create this file manually ).
Have you tried running bin/genaliases? That may do something. You shouldn't have had to create /var/lib/mailman/data/aliases. The fact that you did says newlist is writing aliases elsewhere.
Could this just be a bug in the RHEL5 package? I can work around this by just manually updating aliases, however I'd like to try to find out if maybe I did something wrong.
I don't think it's a bug, but RedHat relocates many things for FHS compliance for SELinux. I think it's just a matter of finding where things are.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Check the permissions and ownership of the aliases file (not in front of my install, but documentation tells you how it should be set - I believe on my install the group ownership is list)
Also - I believe your Postfix main.cf file needs to have an entry pointing to an additional aliases file, instead of updating the /etc/aliases file. However, on a fresh install a few days ago (my first 2.1.11 install), I found that it's dropping the aliases file that it updates in something like /var/lib/mailman. That was new to me, but seemed to work out of the box.
So go to your root directory and do a
#find -name aliases
and see if you have multiple aliases files, maybe it's hanging out in the mailman install directory.
-----Original Message----- From: mailman-users-bounces+scott=916networks.com@python.org [mailto:mailman-users-bounces+scott=916networks.com@python.org] On Behalf Of Mark Ratcliff Sent: Friday, August 21, 2009 10:29 AM To: mailman-users@python.org Subject: [Mailman-Users] Mailman not automatically updating its aliases file
Hi, I was recently tasked with setting up a new mailman server.
We installed mm2.1.9 via yum on a RHEL5.3 server with postfix installed.
varprefix=/var/lib/mailman and prefix =/usr/lib/mailman.
This is what I have for custom lines in my mm_cfg.py:
DEFAULT_EMAIL_HOST = 'mm server name' DEFAULT_URL_HOST = 'mm server name'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
MTA = 'Postfix' VIRTUAL_HOST_OVERVIEW = 0 OWNERS_CAN_ENABLE_PERSONALIZATION = 1
My problem is that whenever I use the newlist command and I create a list, it doesnt automatically update the aliases file. According to the install documentation on the mailman website, I only had to do a few things including adding MTA='Postfix', etc. Are there any other settings that I need to check on in order to make sure it is working?
Thanks for any replies.
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/scott%40916networks.com
Security Policy: http://wiki.list.org/x/QIA9
This worked. I was able to find where it was being written to, which was /etc/mailman/aliases when I was expecting it to be in /var/lib/mailman/data. All I have to do is point postfix to this directory and all will be well.
Thanks!
-----Original Message----- From: Scott Race [mailto:scott@916networks.com] Sent: Friday, August 21, 2009 8:26 PM To: Mark Ratcliff Cc: mailman-users@python.org Subject: RE: Mailman not automatically updating its aliases file
Check the permissions and ownership of the aliases file (not in front of my install, but documentation tells you how it should be set - I believe on my install the group ownership is list)
Also - I believe your Postfix main.cf file needs to have an entry pointing to an additional aliases file, instead of updating the /etc/aliases file. However, on a fresh install a few days ago (my first 2.1.11 install), I found that it's dropping the aliases file that it updates in something like /var/lib/mailman. That was new to me, but seemed to work out of the box.
So go to your root directory and do a
#find -name aliases
and see if you have multiple aliases files, maybe it's hanging out in the mailman install directory.
-----Original Message----- From: mailman-users-bounces+scott=916networks.com@python.org [mailto:mailman-users-bounces+scott=916networks.com@python.org] On Behalf Of Mark Ratcliff Sent: Friday, August 21, 2009 10:29 AM To: mailman-users@python.org Subject: [Mailman-Users] Mailman not automatically updating its aliases file
Hi, I was recently tasked with setting up a new mailman server.
We installed mm2.1.9 via yum on a RHEL5.3 server with postfix installed.
varprefix=/var/lib/mailman and prefix =/usr/lib/mailman.
This is what I have for custom lines in my mm_cfg.py:
DEFAULT_EMAIL_HOST = 'mm server name' DEFAULT_URL_HOST = 'mm server name'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
MTA = 'Postfix' VIRTUAL_HOST_OVERVIEW = 0 OWNERS_CAN_ENABLE_PERSONALIZATION = 1
My problem is that whenever I use the newlist command and I create a list, it doesnt automatically update the aliases file. According to the install documentation on the mailman website, I only had to do a few things including adding MTA='Postfix', etc. Are there any other settings that I need to check on in order to make sure it is working?
Thanks for any replies.
Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/scott%40916networks .com
Security Policy: http://wiki.list.org/x/QIA9
participants (3)
-
Mark Ratcliff
-
Mark Sapiro
-
Scott Race