Roman Serbski wrote:
> 
> ----- Original Message -----
> From: "Ken Jones" <[EMAIL PROTECTED]>
> To: "Roman Serbski" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Tuesday, May 08, 2001 2:27 AM
> Subject: Re: problems with ezmlm-idx
> 
> > Roman Serbski wrote:
> > >
> > > Hi all!
> > >
> > > I've installed qmailadmin and everything is OK except ezmlm-idx. I still
> > > receive Internal Server Error while trying to create mailist.
> > > I use FreeBSD 4.2 STABLE, qmail-1.03, vpopmail-4.9.10, qmailadmin-0.45,
> > > ezmlm-idx-0.40, ezmlm-0.53.
> > >
> > > My qmailadmin configuration is:
> > > ./configure \
> > > --enable-vpopmaildir=/home/vpopmail \
> > > --enable-htmldir=/usr/local/www/htdocs \
> > > --enable-cgibindir=/usr/local/www/cgi-bin \
> > > --enable-autoresponder-bin=/usr/local/bin/autorespond \
> > > --enable-ezmlmdir=/usr/local/bin \
> > > --enable-ezmlmidx=y
> > >
> > > Installation is OK, everything is operatable (I could login, add user,
> > > create alias, whatever) but I've been stuck with mailist adding...
> > >
> > > Here is my Apache log:
> > > [Mon May  7 11:42:06 2001] [error] Premature end of script headers:
> > > /usr/local/www/cgi-bin/qmailadmin
> > > ezmlm-make: illegal option -- 5
> > > ezmlm-make: usage: ezmlm-make [ -aApP ] dir dot local host
> > >
> > > I looked through mailist archive and I found that I should make some
> changes
> > > in mailinglist.c... but it was solution for old versions of
> qmailadmin...
> > > what about qmailadmin-0.45??? Any patches?
> > >
> > > Plz help me.
> > > Thank you very much!
> > >
> > > ----
> > > Ciao,
> > > Roman Serbski
> > > mailto:[EMAIL PROTECTED]
> >
> > It sounds like qmailadmin thinks you have ezmlm-idx installed.
> > -5 is an idx option. The configure script looks for
> > ezmlm-moderate in the ezmlm dir (default is /usr/local/bin/ezmlm)
> >
> > Ken Jones
> >
> 
> Hi Ken!
> 
> Thanks for answer.
> As I understood from your reply qmailadmin thinks that I have emzlm
> installed but it takes ezmlm-idx's ezmlm-moderate and that's why it
> generates an error?
> What could be a solution for my problem - to reinstall ezmlm/ezmlm-idx or to
> delete ezmlm-idx?
> I installed both ezmlm and ezmlm-idx from ports.
> I do not have /usr/local/bin/ezmlm directory - all ezmlm binaries are in
> /usr/local/bin dir (and I defined this directory during qmailadmin
> installation ./configure --enable-ezmlmdir=/usr/local/bin):
> 
> # ls -al /usr/local/bin | grep ezmlm
> -r-xr-xr-x   1 root  wheel      876 Dec 19 13:42 ezmlm-accept
> -r-xr-xr-x   1 root  wheel    28768 Dec 19 13:42 ezmlm-archive
> -r-xr-xr-x   1 root  wheel    46292 Dec 19 13:42 ezmlm-cgi
> -r-xr-xr-x   1 root  wheel    21042 Dec 19 13:42 ezmlm-check
> -r-xr-xr-x   1 root  wheel    30540 Dec 19 13:42 ezmlm-clean
> -r-xr-xr-x   1 root  wheel    23372 Dec 19 13:42 ezmlm-cron
> -r-xr-xr-x   1 root  wheel    19172 Dec 19 13:42 ezmlm-gate
> -r-xr-xr-x   1 root  wheel    59324 Dec 19 13:42 ezmlm-get
> -r-xr-xr-x   1 root  wheel     3070 Dec 19 13:42 ezmlm-glconf
> -r-xr-xr-x   1 root  wheel    25748 Dec 19 13:42 ezmlm-idx
> -r-xr-xr-x   1 root  wheel    16032 Dec 19 13:42 ezmlm-issubn
> -r-xr-xr-x   1 root  wheel    14788 Dec 19 13:42 ezmlm-limit
> -r-xr-xr-x   1 root  wheel    11592 May  7 09:07 ezmlm-list
> -r-xr-xr-x   1 root  wheel    20396 May  7 09:07 ezmlm-make
> -r-xr-xr-x   1 root  wheel    30320 May  7 09:07 ezmlm-manage
> -r-xr-xr-x   1 root  wheel      148 Dec 19 13:42 ezmlm-mktab
> -r-xr-xr-x   1 root  wheel    38868 Dec 19 13:42 ezmlm-moderate
> -r-xr-xr-x   1 root  wheel    12780 May  7 09:07 ezmlm-reject
> -r-xr-xr-x   1 root  wheel    38452 Dec 19 13:42 ezmlm-request
> -r-xr-xr-x   1 root  wheel    26280 May  7 09:07 ezmlm-return
> -r-xr-xr-x   1 root  wheel    22588 May  7 09:07 ezmlm-send
> -r-xr-xr-x   1 root  wheel    23536 Dec 19 13:42 ezmlm-split
> -r-xr-xr-x   1 root  wheel    38056 Dec 19 13:42 ezmlm-store
> -r-xr-xr-x   1 root  wheel    15132 May  7 09:07 ezmlm-sub
> -r-xr-xr-x   1 root  wheel    76983 Dec 19 13:42 ezmlm-test
> -r-xr-xr-x   1 root  wheel    16092 Dec 19 13:42 ezmlm-tstdig
> -r-xr-xr-x   1 root  wheel    15132 May  7 09:07 ezmlm-unsub
> -r-xr-xr-x   1 root  wheel    25440 May  7 09:07 ezmlm-warn
> -r-xr-xr-x   1 root  wheel    12288 May  7 09:07 ezmlm-weed
> 
> BTW should I use ezmlm or ezmlm-idx or both?

Ah ha. perhaps we are looking at an untested "ports" installation
testing problem. I'm not sure if qmailadmin/vpopmail have been 
tested in your configuration. So I'm not surprised that you are
having problems. 

I bet if you removed what you currently have, and install
everything from the source tar balls, it would work.

It would be good to record which version of everything
you currently have, os, qmail, vpopmail, qmailadmin, ezmlm,
and what installation method you used "ports" or "source".

>From there we can start to track down the problem and
look for a fix. Here is how I would start testing..

1) attempt to make a mailing list in qmailadmin, so you
   can reproduce the error. If you want extra credit, 
   test each of the various options.

   Since you have ezmlm-idx installed from ports, and
   set qmailadmin to look at /usr/local/bin, then at
   least qmailadmin was able to detect you have ezmlm-idx,
  
2) Try to collect the qmailadmin error message.
   Extra credit is to search the source code, hint: 
   look mailinglist.c:

        pid=fork();
        if (pid==0) {
                sprintf(TmpBuf1, "%s/ezmlm-make", EZMLMDIR);
                sprintf(TmpBuf2, "%s/%s", RealDir, ActionUser);
                sprintf(TmpBuf3, "%s/.qmail-%s", RealDir, ActionUser);
           ...  then ...
                execv(TmpBuf1, arguments);

before you execv, you can have it print out the entire arguments list.
You can use 
fprintf(actout,"format string", values... );
Just loop through the arguments character pointers.
fprintf(actout, "%s %s %s ...\n", arguments[0], arguments[1],
arguments[2]);
or something like that.

3) Run the ezmlm-make command on the command line and see if you can
replicate
   the error. Once you do that, you can look up the details of
ezmlm-make and
    see if you can find the error. And hopefully find a fix.

4) If you are successful at that, then we can fix the source code.

The other option, is to start with the latest versions of the source
code
and test. The problem you are seeing might already be fixed in newer
versions.

If that is the case, then we can compile new versions and submit them
to the ports folks. Keep it updated :)

Ken Jones

Reply via email to