Perhaps the only way around this one is to use a cron job!

The PHP script writes to a text file commands... Each line would look like
this
    adduser [EMAIL PROTECTED] password
    deluser [EMAIL PROTECTED]

A PHP script, ran as root, from cron could then use the commands from that
file and exec the vpopmail/bin/v* commands with the correct commands.

Paul

----- Original Message -----
From: "IceBerg" <[EMAIL PROTECTED]>
To: "Paul - Zenith Tech Inc" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, November 12, 2001 3:36 PM
Subject: Re: vpopmail with PHP


> I have tried this and there are problems with it.  You need to run the web
> server as user vpopmail and group vchkpw, all you files that are to be
> served also need to be apopriatly owned this way too.  Unlinek with nobody
> the web server cant access files as vpopmail unless it has permisions to
do
> so.  Adding nobody to group vchkpw c auses other issues so avoid that.  On
> top of this there are also very sever security issues that this cuses wich
> is why Im trying to avoid it.  Inter7.com has a cgi wich may be better
> suited for what you want called vqadim:
> http://www.inter7.com/vqadmin
> So far I havent had luck with it ti spews out posix errors on my linux box
> and qmailadmin spews out undefined referances so Ive never gotten that to
> run either.  The other option is to use php so exed sudo the vpopmail
> applications.
>
> Let me know what you get working Im surious since Im having similar
> problems.  qmail/vpopmail administration is very linux/php unfriendly it
> seems.
>
>
> Bryan
>
>
> on 11/11/01 1:30 PM, Paul - Zenith Tech Inc at [EMAIL PROTECTED] wrote:
>
> > Hi,
> >
> > Has anybody used the vpopmail libraries through a PHP script?
> >
> > When trying to add a domain, I get this error from PHP
> >
> > vpopmail error: Unable to chdir to vpopmail/domains directory
> >
> > I changed the permission on domains (and the subdirs) to 777 but this
made
> > no difference.
> >
> > Does anybody know the cause of this?
> >
> > Thanks,
> > Paul
> >
> >
> >
>
>

Reply via email to