Re: [Mailman-Users] First-time poster...
- Original Message - From: John Dennis [EMAIL PROTECTED] Short of that the only other things I can think of would be to strace (assuming you're on a system with strace, e.g. Linux) the postfix process and seeing where the failure occurs and/or to look at the postfix code that performs the lookup and see exactly what c lib functions it's calling and what triggers it to return a failure. Doh, ended up being a chroot issue in master.cf. Thanks John, Mark, and Dan for the responses, and my apologies to the list for the noise... Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] First-time poster...
Hello list members! I have setup a list server running on Fedora Core 2, with Postfix 2.2.3, Mailman 2.1.5, and Python 2.3.4. I think I followed the Mailman setup and configuration guidelines correctly, but am having a problem that I cannot find resolution to via google nor by a search of the Mailman list archives. When sending a message to a test list, the message sits in the queue and Postfix reports in the maillog: Jun 6 09:04:55 lists postfix/qmgr[19892]: E16EA6FE2C: from=[EMAIL PROTECTED], size=1215, nrcpt=1 (queue active) Jun 6 09:04:55 lists postfix/local[19915]: warning: cannot find alias database owner for hash:/usr/local/mailman/data/aliases(0,34100) The permissions on the aliases* files are: ls -l /usr/local/mailman/data/alias* -rw-rw 1 mailman mailman 107000 Jun 6 08:59 aliases -rw-r- 1 mailman mailman 167936 Jun 6 08:59 aliases.db If anyone has any suggestions on how I might resolve this, I would greatly appreciate the feedback. Regards, Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
Bill Landry wrote: I have setup a list server running on Fedora Core 2, with Postfix 2.2.3, Mailman 2.1.5, and Python 2.3.4. I think I followed the Mailman setup and configuration guidelines correctly, but am having a problem that I cannot find resolution to via google nor by a search of the Mailman list archives. When sending a message to a test list, the message sits in the queue and Postfix queue? Postfix reports in the maillog: Jun 6 09:04:55 lists postfix/qmgr[19892]: E16EA6FE2C: from=[EMAIL PROTECTED], size=1215, nrcpt=1 (queue active) This looks like mailman has received the post and is trying to notify the owner/moderator (or maybe deliver the post if there is only one recipient). Listname-bounces is the usual envelope sender for messages from Mailman. Jun 6 09:04:55 lists postfix/local[19915]: warning: cannot find alias database owner for hash:/usr/local/mailman/data/aliases(0,34100) I don't know postfix and am not sure what this means. The permissions on the aliases* files are: ls -l /usr/local/mailman/data/alias* -rw-rw 1 mailman mailman 107000 Jun 6 08:59 aliases -rw-r- 1 mailman mailman 167936 Jun 6 08:59 aliases.db aliases.db should be group writable and I think is normally owned by root which may relate to the above log message. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
- Original Message - From: Mark Sapiro [EMAIL PROTECTED] I have setup a list server running on Fedora Core 2, with Postfix 2.2.3, Mailman 2.1.5, and Python 2.3.4. I think I followed the Mailman setup and configuration guidelines correctly, but am having a problem that I cannot find resolution to via google nor by a search of the Mailman list archives. When sending a message to a test list, the message sits in the queue and Postfix queue? Yes. Postfix reports in the maillog: Jun 6 09:04:55 lists postfix/qmgr[19892]: E16EA6FE2C: from=[EMAIL PROTECTED], size=1215, nrcpt=1 (queue active) This looks like mailman has received the post and is trying to notify the owner/moderator (or maybe deliver the post if there is only one recipient). Listname-bounces is the usual envelope sender for messages from Mailman. Jun 6 09:04:55 lists postfix/local[19915]: warning: cannot find alias database owner for hash:/usr/local/mailman/data/aliases(0,34100) I don't know postfix and am not sure what this means. The permissions on the aliases* files are: ls -l /usr/local/mailman/data/alias* -rw-rw 1 mailman mailman 107000 Jun 6 08:59 aliases -rw-r- 1 mailman mailman 167936 Jun 6 08:59 aliases.db aliases.db should be group writable and I think is normally owned by root which may relate to the above log message. I change the aliases.db to be group writeable, and even tried setting the ownership to root:mailman, but bin/check_perms did not like that and set the permission back to mailman:mailman. The aliase* files now look like (with no bin/check_perms issues reported): -rw-rw-r-- 1 mailman mailman 107000 Jun 6 08:59 aliases -rw-rw-r-- 1 mailman mailman 167936 Jun 6 08:59 aliases.db but I am still seeing the same problem reported in the maillog: Jun 6 10:52:07 lists postfix/local[20108]: warning: cannot find alias database owner for hash:/usr/local/mailman/data/aliases(0,34100) Any other thoughts, ideas, suggestions...? Thanks, Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
Bill Landry wrote:
I change the aliases.db to be group writeable, and even tried setting the
ownership to root:mailman, but bin/check_perms did not like that and set
the permission back to mailman:mailman. The aliase* files now look like
(with no bin/check_perms issues reported):
-rw-rw-r-- 1 mailman mailman 107000 Jun 6 08:59 aliases
-rw-rw-r-- 1 mailman mailman 167936 Jun 6 08:59 aliases.db
but I am still seeing the same problem reported in the maillog:
Jun 6 10:52:07 lists postfix/local[20108]: warning: cannot find alias
database owner for hash:/usr/local/mailman/data/aliases(0,34100)
What happens if you leave the ownership as root:mailman in spite of
check_perms?
Have you followed the Postfix setup instructions at for example
http://mailman.sourceforge.net/mailman-install/node12.html (mirrors at
http://www.gnu.org/software/mailman/mailman-install/node12.html and
http://www.list.org/mailman-install/node12.html
In any case, this appears to be a postfix configuration issue. A google
search for cannot find alias database owner turns up two links to a
postfix module alias.c, the relevant piece of which is:
/*
* DELIVERY RIGHTS
*
* What rights to use for |command and /file/name deliveries? The
* command and file code will use default rights when the alias
* database is owned by root, otherwise it will use the rights of
* the alias database owner.
*/
if ((alias_uid = dict_owner(*cpp)) == 0) {
alias_pwd = 0;
RESET_USER_ATTR(usr_attr, state.level);
} else {
if ((alias_pwd = mypwuid(alias_uid)) == 0) {
msg_warn(cannot find alias database owner for %s, *cpp);
*statusp = defer_append(BOUNCE_FLAG_KEEP,
BOUNCE_ATTR(state.msg_attr),
cannot find alias database owner);
return (YES);
}
SET_USER_ATTR(usr_attr, alias_pwd, state.level);
}
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
- Original Message - From: Mark Sapiro [EMAIL PROTECTED] What happens if you leave the ownership as root:mailman in spite of check_perms? Then I get the following in the maillog: Jun 6 12:22:45 lists postfix/local[20474]: 711426FE2C: to=[EMAIL PROTECTED], relay=local, delay=1, status=bounced (Command died with status 1: /usr/local/mailman/mail/mailman post curtistest) and I get back an undeliverable message. Have you followed the Postfix setup instructions at for example http://mailman.sourceforge.net/mailman-install/node12.html (mirrors at http://www.gnu.org/software/mailman/mailman-install/node12.html and http://www.list.org/mailman-install/node12.html Yes. In any case, this appears to be a postfix configuration issue. A google search for cannot find alias database owner turns up two links to a postfix module alias.c, the relevant piece of which is: /* * DELIVERY RIGHTS Not sure what to do with this code snippet. If you have any further advice based on the Command died with status 1 I receive when setting the aliases.db perms to root:mailman, please let me know. Otherwise, I will post this to the Postfix list to see what they have to say. Thanks for your comments and suggestions! Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
On Mon, 2005-06-06 at 11:46 -0700, Mark Sapiro wrote: Bill Landry wrote: Jun 6 10:52:07 lists postfix/local[20108]: warning: cannot find alias database owner for hash:/usr/local/mailman/data/aliases(0,34100) In any case, this appears to be a postfix configuration issue. A google search for cannot find alias database owner turns up two links to a postfix module alias.c, the relevant piece of which is: I don't think this is a postfix configuration issue, but rather a problem with user lookup's. What the code in question is doing is getting the user id (uid) of the owner of of the alias file and then mapping it to an account. For some reason that's failing. On the machine that postfix is running on you should verify the mailman account exists. (what does the command id mailman return?). Are you running postfix and mailman on the same machine. Do you have any of the files on an NFS mount? It seems very odd that ls -l prints out mailman as the owner but postfix can't perform the same lookup. Are you running a NSCD (Name Service Cache Daemon)? If so, maybe the cache isn't refreshed. Have you tried restarting postfix? Is mailman in /etc/shadow on the machine postfix is running on? -- John Dennis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
Bill Landry wrote: - Original Message - From: Mark Sapiro [EMAIL PROTECTED] What happens if you leave the ownership as root:mailman in spite of check_perms? Then I get the following in the maillog: Jun 6 12:22:45 lists postfix/local[20474]: 711426FE2C: to=[EMAIL PROTECTED], relay=local, delay=1, status=bounced (Command died with status 1: /usr/local/mailman/mail/mailman post curtistest) and I get back an undeliverable message. And did that say anything about a group mismatch error? Or is there anything in Mailman's 'error' log? If you're getting group mismatch errors, see FAQ article 6.16 Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Have you followed the Postfix setup instructions at for example http://mailman.sourceforge.net/mailman-install/node12.html (mirrors at http://www.gnu.org/software/mailman/mailman-install/node12.html and http://www.list.org/mailman-install/node12.html Yes. In any case, this appears to be a postfix configuration issue. A google search for cannot find alias database owner turns up two links to a postfix module alias.c, the relevant piece of which is: /* * DELIVERY RIGHTS Not sure what to do with this code snippet. Nor I. I only mentioned it because the comment seems to indicate that if the aliases.db (and aliases) is owned by mailman, postfix has to be told something about what rights to give mailman. If you have any further advice based on the Command died with status 1 I receive when setting the aliases.db perms to root:mailman, please let me know. Otherwise, I will post this to the Postfix list to see what they have to say. As above, I think setting the owner of the aliases to root allowed postfix to pipe the message to the mailman wrapper which then died. What usually causes this is the group mismatch error. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
- Original Message - From: John Dennis [EMAIL PROTECTED] On Mon, 2005-06-06 at 11:46 -0700, Mark Sapiro wrote: Bill Landry wrote: Jun 6 10:52:07 lists postfix/local[20108]: warning: cannot find alias database owner for hash:/usr/local/mailman/data/aliases(0,34100) In any case, this appears to be a postfix configuration issue. A google search for cannot find alias database owner turns up two links to a postfix module alias.c, the relevant piece of which is: I don't think this is a postfix configuration issue, but rather a problem with user lookup's. What the code in question is doing is getting the user id (uid) of the owner of of the alias file and then mapping it to an account. For some reason that's failing. On the machine that postfix is running on you should verify the mailman account exists. (what does the command id mailman return?). id mailman uid=41(mailman) gid=41(mailman) groups=41(mailman) Are you running postfix and mailman on the same machine. Yes. Do you have any of the files on an NFS mount? No. It seems very odd that ls -l prints out mailman as the owner but postfix can't perform the same lookup. Are you running a NSCD (Name Service Cache Daemon)? No. If so, maybe the cache isn't refreshed. Have you tried restarting postfix? Yes, many times. Is mailman in /etc/shadow on the machine postfix is running on? grep mailman /etc/shadow mailman:!!:12327:: Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
On Mon, 2005-06-06 at 12:48 -0700, Mark Sapiro wrote: And did that say anything about a group mismatch error? Or is there anything in Mailman's 'error' log? If you're getting group mismatch errors, see FAQ article 6.16 FWIW, I don't think this problem will manifest itself as a mailman group mismatch error, but I could be wrong. Thinking about this a bit more I suspect Bill may have modified the user/group on the alias file and/or modified the mailman account information while postfix was running, but did not restart postfix. I haven't looked at the postfix code but I wouldn't be surprised if postfix when it starts gets file information on all its input files referenced in main.cf and stores that information. If that information was altered while postfix was running it would likely get confused because it may be using id's that no longer exist. -- John Dennis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
- Original Message - From: John Dennis [EMAIL PROTECTED] On Mon, 2005-06-06 at 12:48 -0700, Mark Sapiro wrote: And did that say anything about a group mismatch error? Or is there anything in Mailman's 'error' log? If you're getting group mismatch errors, see FAQ article 6.16 FWIW, I don't think this problem will manifest itself as a mailman group mismatch error, but I could be wrong. Thinking about this a bit more I suspect Bill may have modified the user/group on the alias file and/or modified the mailman account information while postfix was running, but did not restart postfix. I haven't looked at the postfix code but I wouldn't be surprised if postfix when it starts gets file information on all its input files referenced in main.cf and stores that information. If that information was altered while postfix was running it would likely get confused because it may be using id's that no longer exist. John, I've tried to make sure that I either reload or restart Postfix and Mailman after each config or file permissions change. Thanks for the help guys, it is very much appreciated. I've posted the issue to the Postfix list, so if I can find a resolution there, I will post it back here. If you can think of anything else I should look at, please let me know. Thanks again! Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
On Mon, 2005-06-06 at 13:00 -0700, Bill Landry wrote: O.K. the other things I suggested you check all seem fine. Is mailman in /etc/shadow on the machine postfix is running on? grep mailman /etc/shadow mailman:!!:12327:: Actually /etc/passwd maybe more relevant in this instance. If postfix does not have permission to read /etc/passwd it's look up is going to fail (a non-readable /etc/group may also provoke this). Recall that postfix typically does not run as root for very good reasons. What postfix runs as is configurable. You want to make sure whatever user postfix is running as has permission to read these /etc files. Also typically /etc/passwd and /etc/group are readable by everybody. The only other thing I can think of for you to check is to assure /etc/passwd and /etc/group are readable by the postfix process. Short of that the only other things I can think of would be to strace (assuming you're on a system with strace, e.g. Linux) the postfix process and seeing where the failure occurs and/or to look at the postfix code that performs the lookup and see exactly what c lib functions it's calling and what triggers it to return a failure. -- John Dennis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] First-time poster...
- Original Message - From: John Dennis [EMAIL PROTECTED] On Mon, 2005-06-06 at 13:00 -0700, Bill Landry wrote: O.K. the other things I suggested you check all seem fine. Is mailman in /etc/shadow on the machine postfix is running on? grep mailman /etc/shadow mailman:!!:12327:: Actually /etc/passwd maybe more relevant in this instance. If postfix does not have permission to read /etc/passwd it's look up is going to fail (a non-readable /etc/group may also provoke this). Recall that postfix typically does not run as root for very good reasons. What postfix runs as is configurable. You want to make sure whatever user postfix is running as has permission to read these /etc files. Also typically /etc/passwd and /etc/group are readable by everybody. The only other thing I can think of for you to check is to assure /etc/passwd and /etc/group are readable by the postfix process. Short of that the only other things I can think of would be to strace (assuming you're on a system with strace, e.g. Linux) the postfix process and seeing where the failure occurs and/or to look at the postfix code that performs the lookup and see exactly what c lib functions it's calling and what triggers it to return a failure. This appears to be the standard across all of my RedHat 9/Postfix and Fedora Core3/Postfix servers: ls -l /etc/passwd -rw-r--r-- 1 root root 2172 Jun 6 09:16 /etc/passwd ls -l /etc/group -rw-r--r-- 1 root root 974 Jun 6 13:34 /etc/group My other Postfix servers are function properly, and they all run as mail_owner = postfix, including this particular Mailman server, so I am still a bit baffled by this one. Bill -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
