Re: [Mailman-Users] set gid didn't work?
At 01:14 PM 6/6/01, Amanda wrote: >Well, I thought that was a little weird, so I looked up gid 401, and it >doesn't exist. So I collected some additional information, and >reconfigured with mail gid set to 400 (qmail). I If you have access to /etc/group (or the equivalent), how about just /making up/ a group 401 entry? Call it whatever name you like, like "qmail-oddity". Then configure/make Mailman with gid 401, and hopefully it won't refuse, since now that's a listed group. Good luck! -- Mitch Marks -- Mitchell Marks CUIP Tech Coordinatorhttp://cuip.uchicago.edu CUIP: Chicago Public Schools / Univ. of Chicago Internet Project 5640 S Ellis Ave AAC-045, Univ of Chgo, Chgo IL 60637 Telephone: Ofc 773-702-6041 Fax 702-8212 Home (v.m. only, ok any time) 241-7166 Email: Primary address: [EMAIL PROTECTED] Alternate UofC addresses (use especially to report problems with cuip.uchicago.edu): [EMAIL PROTECTED] and [EMAIL PROTECTED] Off-campus (ISP) address: [EMAIL PROTECTED] Mr. Shrimp felt helplessly caught up in events ... he was just a prawn in their game. Mlle. Snail bought a sports car and had a big "S" painted on the sides ... now everybody seeing her zoom by says "Look at that S-Car go!". -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
> "A" == Amanda <[EMAIL PROTECTED]> writes: A> have a fairly keen grasp on MacOS 7/8x Glad to have helped. Now sometime I'll get you to help me figure out why my G4 tower running MacOS 9.1 keeps blinding itself to my USB Palm cradle connected through a Belkin 4-port hub. Whenever I reboot the Mac or it wakes up from its "power nap", I have to unplug the cradle's USB connector from the hub, and re-insert it. /Then/ it'll hot sync. :) any-sufficiently-advanced-science-appears-as-magic-ly y'rs, -Barry -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
Thanks for the recommend! If I ever get my head above water enough to go shopping for another book (much less read!) I will certainly consider it. I wish I'd gotten your email two hours ago... it might have saved me about half of the time that I spent figuratively crawling on my hands and knees through the system with a flashlight and a magnifying glass. (The other half was actually locating the pesky little critter and eradicating it.) Barry, et al, I really appreciate all the suggestions and ideas and support. Because of your (all of you's) input over the last few days I've gotten one step closer to actually getting my job done. And believe me, I will be relieved to move on to other things! *sigh* I've spent the last sixteen years with a keyboard in my hands. I've learned various programming languages, can make DOS do backflips, actually have beaten (and continue to beat) Windows in its various incarnations into terrified submission, have a fairly keen grasp on MacOS 7/8x, and have a cute little certificate naming me "Hardware Goddess of the Month," can run circles around some of the Novell administrators to whom I used to report - I know that stuff backwards and forwards in my sleep blindfolded with one hand tied behind my back . but Linux is kicking my butt. Classes, tutorials, and manuals - even a fair amount of user-end experience - cannot even begin to prepare a person for the bizarre and apparently random and stupid things that happen in a real-life linux admin environment. I hate it. I take some consolation in the fact that the gurus who gave me all the skinny on qmail in the first place were just as baffled by its behaviour as I was. And the folks who so highly recommended Mandrake to me have been thoroughly confused by the things that kept breaking during configuration ... ... if they can't make it work, what makes me think I can?? Makes me wonder why the freaking heck I ever signed up for this project. Sorry... tonight I will have a beer. Or three. I think I've earned it. =) Amanda "Barry A. Warsaw" wrote: > Short answer: I don't think it's a Mailman issue, per se. I think > you've still got Qmail configuration problems. > > I don't know how much you know about Unix processes, user ids, and > group ids, but an excellent reference on the subject (and really > almost /all/ things *nix) is W. Richard Stevens' "Advanced Programming > in the UNIX Environment". Very highly recommended. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
You are NOT going to believe this one. I'm still not quite sure how this happened... I *looked* for a gid of 401 ... and I looked at all the users the system would list... No matter what I did, I couldn't get the alias user to show up at all, short of a sledgehammer. qmail has a user named alias which is supposed to be created in the "nofiles" group. I went back to my own logs and when I created the users, I put alias and the other appropriate qmail users in the nofiles group. However, for some reason it didn't "take" - it would not belong to the nofiles group. I surmise that the system didn't think it belonged to ANY group,and so gave it its own group (?) ... and since nobody specified a text name for that group, the group wouldn't show up. When I finally DID get it to show me the alias user, guess what its group number was? 401. I'm guessing that having a broken user "alias" would not affect other mail going through qmail because the other things don't require the gid? Hmm. It's strange ... because qmail's been working beautifully with the alias user set wrong ... presumably this whole time? Ergh. ::off to rip out every instance of gid 401 she can locate:: =) Amanda "I don't get paid enough for this" Amanda wrote: > Amanda wrote: > > > Everything I "fix" breaks something else so far. I'm engaging in enough > > growling lately that the editors are frightened of me... > > Uy. No kidding. > Somebody please offer me some advice here... > Let me start from the beginning. [Again.] > > I have an HP Vectra XU archaic piece of junk running Mandrake 8 (kernel > 2.4.3). It is running qmail 1.03 and Apache 1.3.20. Mail, telnet, and web > services are functioning as expected. I installed Mailman 2.0.5, > according to the documentation, made the proper qmail aliases, ran > crontab, added the CGI and alias stuff to httpd.conf, etc, etc. > > When I initially installed the program, I ran it with-mail-gid=12 (mail). > Mail was going to the list admin, and I could access and modify the admin > page without issue. Later I discovered that the program wasn't passing > mail to the list, so I looked in the logs. I was getting this error > message: > > Mailman mail-wrapper: Failure to exec script. > WANTED gid 12, GOT gid 401. (Reconfigure to take 401?) > > qmail: 991698598.174168 delivery 5: deferral: > Failure_to_exec_script._WANTED_gid_12, > _GOT_gid_401.__(Reconfigure_to_take_401?) > > Well, I thought that was a little weird, so I looked up gid 401, and it > doesn't exist. So I collected some additional information, and > reconfigured with mail gid set to 400 (qmail). It still wasn't working - > at this point the error message logged was: > > Mailman mail-wrapper: Failure to exec script. > WANTED gid 400, GOT gid 401. (Reconfigure to take 401?) > > qmail: 991698598.174168 delivery 5: deferral: > Failure_to_exec_script._WANTED_gid_400, > _GOT_gid_401.__(Reconfigure_to_take_401?) > > So I attempted to reconfigure with gid 401. Then I got: > [ No existing group found for the mail_wrapper program. This is the group > that > your mail delivery agent runs under, and uses to run filter programs. You > might want to specify an existing group with the --with-mail-gid > configure option. Please see your mail agent's documentation, and the > install file for details. ] > > So I attempted to nuke and pave. I ran make clean again, nuked the > /home/mailman directory, ran configure with the mail gid set to 400, ran > make install, exactly according to the reinstall instructions, did the > hokey-pokey, made sure the computer was facing east, paid a shaman to do > a dance to the mailing list gods... > ...absolutely no change in the behaviour of the program: > > Mailman mail-wrapper: Failure to exec script. > WANTED gid 400, GOT gid 401. (Reconfigure to take 401?) > > qmail: 991698598.174168 delivery 5: deferral: > Failure_to_exec_script._WANTED_gid_400, > _GOT_gid_401.__(Reconfigure_to_take_401?) > > What I want to know is if anybody can answer any of these questions for > me: > > - Where in the name of common sense is gid 401? When it says "GOT gid > 401" where is it getting it? Who/what is passing a gid at that point? > - Did I actually do enough to get a clean install of Mm, or are there > additional steps I can take to ensure that I'm really getting a clean > install? > - Are there any suggestions for installing and configuring this thing in > a manner in which it might actually work? > > We're now getting to the point where my head's going to be on a chopping > block if I cannot make it work. I'm more than slightly panicked about > that. > > Thanks, > =) > Amanda -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
Short answer: I don't think it's a Mailman issue, per se. I think you've still got Qmail configuration problems. I don't know how much you know about Unix processes, user ids, and group ids, but an excellent reference on the subject (and really almost /all/ things *nix) is W. Richard Stevens' "Advanced Programming in the UNIX Environment". Very highly recommended. > "A" == Amanda <[EMAIL PROTECTED]> writes: A> - Where in the name of common sense is gid 401? When it says A> "GOT gid 401" where is it getting it? Who/what is passing a gid A> at that point? When an MTA, e.g. Qmail in your case, tries to deliver a message to a program, it will execute that program with certain user and group ids. Each MTA has a different way of deciding which uid and gid to use when running a filter program. I'm not sure about the exact details of Qmail, but there /has/ to be a way to configure Qmail to change the uid and gid. For Mailman purposes, we don't care about the uid. In your case, Qmail is executing Mailman's mail-wrapper program with gid 401, which Mailman determines through the getgid() system call. Note, there's no gid "getting passed" here; the (real) gid is an attribute of a Unix process. Now, Mailman's --with-mail-gid configure option says essentially sets the MAIL_GID C macro to the numeric equivalent of the option's value. Thus, say you've got a line like the following in your /etc/group file: qmail:x:400: This is saying that the symbolic group name `qmail' has a gid of 400. --with-mail-gid will allow you to use either a symbolic group name or a numeric group id, but it will not allow you to specify one that isn't in your /etc/group file. So, the Qmail configuration problem you've got is that it's attempting to execute filter programs using a gid that's not in your /etc/group file. You can either reconfigure Qmail to execute filter programs with group=qmail/gid=400, or you can add a dummy group to your /etc/group file like so: qmailprogs:x:401: (Note the exact format of /etc/group, or even whether you /use/ an /etc/group as opposed to a NIS map or some other network information system, is site dependent). If you go with the first solution, you'll then want to recompile Mailman --with-mail-gid=qmail but if you go with the second solution, you'll want to recompile --with-mail-gid=qmailprogs There's one more solution that might help: forget --with-mail-gid and use a "make variable". Because of the --with-mail-gid restriction that the numeric gid must be in /etc/group, and because for you it is not, let's assume you can't actually modify the /etc/group file, and you can't get qmail to execute programs with gid 400. In this case, after a "make clean", re-run Mailman's configure script without the --with-mail-gid switch. When you then run "make install", do it like this instead: % make MAIL_GID=401 install or perhaps % MAIL_GID=401 make install (if you're using a Bourne shell derivative, like bash). A> - Did I actually do enough to get a clean A> install of Mm, or are there additional steps I can take to A> ensure that I'm really getting a clean install? A "make clean" ought to be enough to solve this particular problem, although even that may not be necessary. Just rerunning configure, "make install" ought to be enough -- when you figure out the right gid to use! A> - Are there A> any suggestions for installing and configuring this thing in a A> manner in which it might actually work? I hope the above explains the issues in enough details to get it working. Just to re-iterate, I don't believe you have a Mailman problem, but instead, qmail isn't quite configured correctly. A> We're now getting to the point where my head's going to be on a A> chopping block if I cannot make it work. I'm more than slightly A> panicked about that. Well, we wouldn't want that! Hopefully you can now get things working. Cheers, -Barry -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
Amanda wrote: > Everything I "fix" breaks something else so far. I'm engaging in enough > growling lately that the editors are frightened of me... Uy. No kidding. Somebody please offer me some advice here... Let me start from the beginning. [Again.] I have an HP Vectra XU archaic piece of junk running Mandrake 8 (kernel 2.4.3). It is running qmail 1.03 and Apache 1.3.20. Mail, telnet, and web services are functioning as expected. I installed Mailman 2.0.5, according to the documentation, made the proper qmail aliases, ran crontab, added the CGI and alias stuff to httpd.conf, etc, etc. When I initially installed the program, I ran it with-mail-gid=12 (mail). Mail was going to the list admin, and I could access and modify the admin page without issue. Later I discovered that the program wasn't passing mail to the list, so I looked in the logs. I was getting this error message: > Mailman mail-wrapper: Failure to exec script. WANTED gid 12, GOT gid 401. (Reconfigure to take 401?) > qmail: 991698598.174168 delivery 5: deferral: Failure_to_exec_script._WANTED_gid_12, _GOT_gid_401.__(Reconfigure_to_take_401?) Well, I thought that was a little weird, so I looked up gid 401, and it doesn't exist. So I collected some additional information, and reconfigured with mail gid set to 400 (qmail). It still wasn't working - at this point the error message logged was: > Mailman mail-wrapper: Failure to exec script. WANTED gid 400, GOT gid 401. (Reconfigure to take 401?) > qmail: 991698598.174168 delivery 5: deferral: Failure_to_exec_script._WANTED_gid_400, _GOT_gid_401.__(Reconfigure_to_take_401?) So I attempted to reconfigure with gid 401. Then I got: [ No existing group found for the mail_wrapper program. This is the group that your mail delivery agent runs under, and uses to run filter programs. You might want to specify an existing group with the --with-mail-gid configure option. Please see your mail agent's documentation, and the install file for details. ] So I attempted to nuke and pave. I ran make clean again, nuked the /home/mailman directory, ran configure with the mail gid set to 400, ran make install, exactly according to the reinstall instructions, did the hokey-pokey, made sure the computer was facing east, paid a shaman to do a dance to the mailing list gods... ...absolutely no change in the behaviour of the program: > Mailman mail-wrapper: Failure to exec script. WANTED gid 400, GOT gid 401. (Reconfigure to take 401?) > qmail: 991698598.174168 delivery 5: deferral: Failure_to_exec_script._WANTED_gid_400, _GOT_gid_401.__(Reconfigure_to_take_401?) What I want to know is if anybody can answer any of these questions for me: - Where in the name of common sense is gid 401? When it says "GOT gid 401" where is it getting it? Who/what is passing a gid at that point? - Did I actually do enough to get a clean install of Mm, or are there additional steps I can take to ensure that I'm really getting a clean install? - Are there any suggestions for installing and configuring this thing in a manner in which it might actually work? We're now getting to the point where my head's going to be on a chopping block if I cannot make it work. I'm more than slightly panicked about that. Thanks, =) Amanda -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
> Oh darn, you're right. I forgot that configure checks even numeric > gids with getgrgid(). So it /does/ complain if there's no entry in > /etc/group for the argument to --with-mail-gid. > > A> So, it ain't working. Mail goes into mailman and is never seen > A> again. Argh. > > Did you set up the crontab? Yuh. I did that. :-) Everything I "fix" breaks something else so far. I'm engaging in enough growling lately that the editors are frightened of me... =) Amanda -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
> "A" == Amanda <[EMAIL PROTECTED]> writes: >> A> I couldn't get it to compile when I used >> --with-mail-gid=401. >> Hmm, what kind of error did you get? A> C&P from an earlier post I made to this list: Unfortunately... A> it apparently won't configure that way. When I run A> ./configure --with-mail-gid=401 it says: [ No existing A> group found for the mail_wrapper program. This is the A> group that your mail delivery agent runs under, and uses to run A> filter programs. You might want to specify an existing group A> with the --with-mail-gid configure option. Please see your A> mail agent's documentation, and the install file for details. ] Oh darn, you're right. I forgot that configure checks even numeric gids with getgrgid(). So it /does/ complain if there's no entry in /etc/group for the argument to --with-mail-gid. A> So, it ain't working. Mail goes into mailman and is never seen A> again. Argh. Did you set up the crontab? -Barry -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
Thank you, Nigel, for the suggestion. :-) Unfortunately... it apparently won't configure that way. When I run ./configure --with-mail-gid=401 it says: [ No existing group found for the mail_wrapper program. This is the group that your mail delivery agent runs under, and uses to run filter programs. You might want to specify an existing group with the --with-mail-gid configure option. Please see your mail agent's documentation, and the install file for details. ] Well ... in the category of other potentially helpful information, when you install qmail you make two groups (not eight, as previously suggested): qmail and nofiles. The mail components appear to run from the qmail group with the various qmail uids. Neither qmail nor nofiles has a gid of 401. To the best of my ability to determine, 401 doesn't exist. The readme.qmail suggests setting it to the GID of qmail, mailman, or nofiles. Tried all three. They all give me failure_to_exec_script:_wanted_gid_[whichever],_got_gid_401. In fact, so far, I've tried the group ids of qmail, nofiles, nobody, mail, mailman, and website. No change except for the "wanted" gid in the log. If it wants 401 and I can't give it 401, what do I do next? (Aside from taking it out in the pasture and shooting it?) ::sigh:: =) Amanda [Further system info as the last time I mentioned this was several posts ago: mailman 2.0.5 on mandrake 8 with qmail 1.03, apache 1.3.20, using xinetd 2.1.8.8, and there's very little else on the machine. It was set up for the express purpose of running mailman.] Nigel Metheringham wrote: > As I recall, qmail hardwires a batch of its uids and gids when its > built, so you can easily have a running qmail using group 401 with no > group 401 defined on your system :-) > > Try > ./configure ... -with-mail-gid=401 > > Nigel. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
I'm coming in in the middle of this thread, but if mail-wrapper is complaining with the following message: > Jun 4 16:49:58 tux Mailman mail-wrapper: Failure to exec > script. WANTED gid 12, GOT gid 401. (Reconfigure to take 401?) then it doesn't matter that there is no group name with gid 401. That actually isn't required either of Mailman or Unix, so just re-run configure with --with-mail-gid=401 and it should work. Now, as to /why/ qmail is executing the wrapper with a gid that has no group name assigned, I couldn't tell you. Hope that helps, -Barry -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
On 05 Jun 2001 08:58:04 -0700, Amanda wrote: > > >Jun 4 16:49:58 tux qmail: 991698598.174168 delivery 5: deferral: > > >Failure_to_exec_script._WANTED_gid_12,_GOT_gid_401.__(Reconfigure_to_take_401?) > > > > > >The kicker is, there *is* no group with gid 401. So I'm a little baffled... > > >What do I need to do to fix this? As I recall, qmail hardwires a batch of its uids and gids when its built, so you can easily have a running qmail using group 401 with no group 401 defined on your system :-) Try ./configure ... -with-mail-gid=401 Nigel. -- [ Nigel Metheringham [EMAIL PROTECTED] ] [ Phone: +44 1423 85 Fax +44 1423 858866 ] [ - Comments in this message are my own and not ITO opinion/policy - ] [ - Security is not an add-on -- security is a way of life - ] -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
Well, you know, I read the docs six times... twice before getting started, once as I was going through the process, and three more times after it broke, trying to figure out what happened. It didn't get any more helpful. What the install documentation says is: [ --with-mail-gid= Specify an alternative group for running scripts via the mail wrapper. can be a list of one or more integer group ids or symbolic group names. The first value in the list that resolves to an existing group is used. By default, the value is the list "other daemon." This is highly system dependent and you must get this right, because the group id is compiled into the mail wrapper program for added security. On systems using sendmail, the sendmail.cf configuration file designates the group id of sendmail processes using the "DefaultUser" option.] Great. So I'm not using sendmail, I'm using qmail. And it doesn't tell me WHICH group I should be looking for. The readme.qmail doesn't specify which group id I should be looking for either. All it tells me is "I must get this right." (That's a LOT of help.) So I made my best SWAG, and apparently not only was I wrong, but the group it tried to set it to (a) wasn't the one I specified, and (b) doesn't exist. Just so you know, I am capable of RTFM ... I'm just not getting the information I need out of it. Next suggestion? =) Amanda Harold Paulson wrote: > Amanda, > > Reread the INSTALL documentation. Everyone messes this up, so they > put it in flashing neon red :) > > - H > > >I'm trying to send messages to my test list and they're not going through. The > >log is giving the following: > > > >Jun 4 16:49:58 tux Mailman mail-wrapper: Failure to exec script. WANTED gid > >12, GOT > >gid 401. (Reconfigure to take 401?) > >Jun 4 16:49:58 tux qmail: 991698598.174168 delivery 5: deferral: > >Failure_to_exec_script._WANTED_gid_12,_GOT_gid_401.__(Reconfigure_to_take_401?) > > > >The kicker is, there *is* no group with gid 401. So I'm a little baffled... > >What do I need to do to fix this? > > > > > >Thanks, > >=) > >Amanda > > -- > > Harold Paulson Sierra Web Design > [EMAIL PROTECTED] http://www.sierraweb.com > VOICE: 775.833.9500 FAX: 810.314.1517 -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] set gid didn't work?
On Jun 4, 17:06PM, Amanda wrote: > I'm trying to send messages to my test list and they're not going through. The > log is giving the following: > > Jun 4 16:49:58 tux Mailman mail-wrapper: Failure to exec script. WANTED gid > 12, GOT > gid 401. (Reconfigure to take 401?) > Jun 4 16:49:58 tux qmail: 991698598.174168 delivery 5: deferral: > Failure_to_exec_script._WANTED_gid_12,_GOT_gid_401.__(Reconfigure_to_take_401?) > > The kicker is, there *is* no group with gid 401. So I'm a little baffled... > What do I need to do to fix this? > > > Thanks, > =) > Amanda > > > -- > Mailman-Users maillist - [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users > *warning, i'm right there with you on the learning curve* That happened to me, too. I reconfigured with the setting --with-mail-gid=nofiles (which for me was the gid the server "GOT"), and everything worked out. (qmail on RH7.0) Hope that leads you in the right direction, Peter Horst -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] set gid didn't work?
I'm trying to send messages to my test list and they're not going through. The log is giving the following: Jun 4 16:49:58 tux Mailman mail-wrapper: Failure to exec script. WANTED gid 12, GOT gid 401. (Reconfigure to take 401?) Jun 4 16:49:58 tux qmail: 991698598.174168 delivery 5: deferral: Failure_to_exec_script._WANTED_gid_12,_GOT_gid_401.__(Reconfigure_to_take_401?) The kicker is, there *is* no group with gid 401. So I'm a little baffled... What do I need to do to fix this? Thanks, =) Amanda -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
