[ Michael S. James writes: ]
> I have just installed majordomo v1.93 (1st time setting up a listserver)
> and all was going well until I subscribed to my test list. I got the
> 'help' & 'list' commands to work initially, so somethings right(?).
> Here are the problems.
> 1. I could not subscribe to my test list w/o specifying the optional
> e-mail address (i.e. subscribe test email@example.com). W/o the address,
> I get back from majordomo,
> >>>>>subscribe test
> and that's all.
A partial reply such as this indicates that Mj is aborting before the
command is completely processed.
> When I sent 'subscribe test firstname.lastname@example.org', majordomo
> told me that I will have to be approved first. I did not knowingly set
> the test list to be moderated. The test.config file has 'no' for moderated.
That's the normal response when the address specified doesn't match the
address in the request message headers. By match, I mean exactly, letter
for letter (but without regard for case), thus email@example.com does
*not* match firstname.lastname@example.org.
> 2. Have several machines on my network and could not subscribing form
> them. Basically, majordomo returns that same type of thing back to me as
> above. What ever I send, majordomo returns back w/o indicating whether
> the command succeded or not, sort of like
> >>>>>lists or >>>>>subscribe test email@example.com
Same problem as #1 I suspect.
> 3. This last problem is coupled with the second problem. All messages
> that I send that I send to majordomo that don't get acknowledged as
> succeeded or not, the return messages stay in /var/spool/mqueue and get
> resent ever 10 minutes or so. I noticed that I kept getting all these
> messages telling me the samething. That's what tipped me off that I
> wasn't really subscribed, so sent a 'who test' command and majordomo told
> me that noone was subscribed. But the who command worked after I sent my
> address in the subcription command.
Undoubtedly because Mj returns an error (i.e. aborts) when your MTA
(e.g. sendmail) attempts to deliver to it, so the MTA queues and retries
the delivery later.
You need to figure out why Mj is aborting. It should be delivering an
abort message if you have "majordomo-owner" aliased to yourself. If it
is and you're not receiving such messages, that's indicative that you've
fallen into the infamous abort loop bug in 1.93 and that Mj doesn't
have write permissions to either the log file and/or the directory that
contains the log file. Fix that and things should work much better.
Dave Wolfe *Not a spokesman for Motorola*
Motorola MMTG 6501 Wm. Cannon Dr. W. OE112 Austin TX 78735-8598