Failed to access config info? [problems w/ qmail]
I'm attempting to use mailman using qmail and running into some problems.
My suspicion is that it's based on the fact that while sendmail runs under UID 0 -- meaning it has no permission problems EVER -- qmail is running under the qmaill userID -- a regular user. In either case, I'm getting the following errors in my log:
Jun 18 00:39:15 fold qmail: 929691555.091267 status: local 4/10 remote 1/20 Jun 18 00:39:16 fold qmail: 929691556.494957 delivery 45: deferral: Traceback_(i nnermost_last):/__File_"/home/mailman/scripts/mailowner",_line_42,_in_?/____mlis t_=_MailList.MailList(sys.argv[1])/__File_"/home/mailman/Mailman/MailList.py",_l ine_60,_in___init__/____self.Load()/__File_"/home/mailman/Mailman/MailList.py",_ line_771,_in_Load/____raise_Errors.MMBadListError,_'Failed_to_access_config_info '/MMBadListError:_Failed_to_access_config_info/ Jun 18 00:39:16 fold qmail: 929691556.495496 status: local 3/10 remote 1/20 Jun 18 00:39:16 fold qmail: 929691556.512682 delivery 43: deferral: Traceback_(innermost_last):/__File_"/home/mailman/scripts/post",_line_45,_in_?/____mlist_=_M ailList.MailList(sys.argv[1])/__File_"/home/mailman/Mailman/MailList.py",_line_6 0,_in___init__/____self.Load()/__File_"/home/mailman/Mailman/MailList.py",_line_ 771,_in_Load/____raise_Errors.MMBadListError,_'Failed_to_access_config_info'/MMB adListError:_Failed_to_access_config_info/ Jun 18 00:39:16 fold qmail: 929691556.513190 status: local 2/10 remote 1/20 Jun 18 00:39:16 fold qmail: 929691556.671985 delivery 46: deferral: Traceback_(innermost_last):/__File_"/home/mailman/scripts/post",_line_45,_in_?/____mlist_=_M ailList.MailList(sys.argv[1])/__File_"/home/mailman/Mailman/MailList.py",_line_6 0,_in___init__/____self.Load()/__File_"/home/mailman/Mailman/MailList.py",_line_ 771,_in_Load/____raise_Errors.MMBadListError,_'Failed_to_access_config_info'/MMB adListError:_Failed_to_access_config_info/ Jun 18 00:39:16 fold qmail: 929691556.672596 status: local 1/10 remote 1/20 Jun 18 00:39:16 fold qmail: 929691556.717041 delivery 47: deferral: Traceback_(innermost_last):/__File_"/home/mailman/scripts/post",_line_45,_in_?/____mlist_=_M ailList.MailList(sys.argv[1])/__File_"/home/mailman/Mailman/MailList.py",_line_6 0,_in___init__/____self.Load()/__File_"/home/mailman/Mailman/MailList.py",_line_ 771,_in_Load/____raise_Errors.MMBadListError,_'Failed_to_access_config_info'/MMB adListError:_Failed_to_access_config_info/
-roy
On Fri, 18 Jun 1999, Roy Rapoport wrote:
Sorry for the followup, but this looks like it's fixed now. What I did to fix it: A) Manually touched ~mailman/logs/error and ~mailman/logs/post B) chmod'ed 777 the two files above. C) Made mail/wrapper mode 6755 (so it's setuid also)
This seems to have gotten me to the point where: A) list administration via the web works; B) email to the list is going through and out.
The only problem remaining is that mass subscribes of users do not result in all the users getting the welcome message. ARGH!
Boy, this was so much easier on sendmail.
-roy
This should be my last email for *at least* two days -- I think I'm done :)
On Fri, 18 Jun 1999, Roy Rapoport wrote:
The only problem remaining is that mass subscribes of users do not result in all the users getting the welcome message. ARGH!
This was pretty bizarre. I think I traced it down to some VERY anomalous behavior on the part of my operating system (Solaris 2.6 on a clone Ultra 1). Specifically:
Take user A and user B. Make them both members of group C.
Make a directory. Make it owned by user A and group C. Make permissions read,write,execute for both user and group, and non-write for others.
Now, here's where things get very very annoying: On the following machines: Solaris 2.5.1, Sparc 2 Solaris 7, Ultra 5 Solaris 2.6, Ultra 5 user B can go into the directory and create a file (touch foo). No problem. This is as I would understand UNIX file permissions. On the following machine: Solaris 2.6, Ultra 1 clone User B gets "touch: foo cannot create".
For what it's worth, there are no patch differences between the U5/2.6 combination above and the 2.6 on this machine. There's some packages to support the different hardware, and my guess is this is where the problem occurs.
I originally solved this by changing the wrappers (admin and wrapper) to be setuid, in addition to setgid, but this was stopping outgoing mail from getting sent out; my guess is qmail was being paranoid.
I just reinstalled mailman (you do *NOT* want to know how many times I've reinstalled mailman over the last 24 hours :) ), and left permissions alone other than changing all directories to permission 777. Not ideal, of course, but it looks like now everything really is working.
Sigh. I'll be talking to Sun support tomorrow and seeing if they have a clue.
-roy
On Fri, 18 Jun 1999, Roy Rapoport wrote:
Sorry for the followup, but this looks like it's fixed now. What I did to fix it: A) Manually touched ~mailman/logs/error and ~mailman/logs/post B) chmod'ed 777 the two files above. C) Made mail/wrapper mode 6755 (so it's setuid also)
This seems to have gotten me to the point where: A) list administration via the web works; B) email to the list is going through and out.
The only problem remaining is that mass subscribes of users do not result in all the users getting the welcome message. ARGH!
Boy, this was so much easier on sendmail.
-roy
This should be my last email for *at least* two days -- I think I'm done :)
On Fri, 18 Jun 1999, Roy Rapoport wrote:
The only problem remaining is that mass subscribes of users do not result in all the users getting the welcome message. ARGH!
This was pretty bizarre. I think I traced it down to some VERY anomalous behavior on the part of my operating system (Solaris 2.6 on a clone Ultra 1). Specifically:
Take user A and user B. Make them both members of group C.
Make a directory. Make it owned by user A and group C. Make permissions read,write,execute for both user and group, and non-write for others.
Now, here's where things get very very annoying: On the following machines: Solaris 2.5.1, Sparc 2 Solaris 7, Ultra 5 Solaris 2.6, Ultra 5 user B can go into the directory and create a file (touch foo). No problem. This is as I would understand UNIX file permissions. On the following machine: Solaris 2.6, Ultra 1 clone User B gets "touch: foo cannot create".
For what it's worth, there are no patch differences between the U5/2.6 combination above and the 2.6 on this machine. There's some packages to support the different hardware, and my guess is this is where the problem occurs.
I originally solved this by changing the wrappers (admin and wrapper) to be setuid, in addition to setgid, but this was stopping outgoing mail from getting sent out; my guess is qmail was being paranoid.
I just reinstalled mailman (you do *NOT* want to know how many times I've reinstalled mailman over the last 24 hours :) ), and left permissions alone other than changing all directories to permission 777. Not ideal, of course, but it looks like now everything really is working.
Sigh. I'll be talking to Sun support tomorrow and seeing if they have a clue.
-roy
participants (1)
-
Roy Rapoport