Ofcource, the programming language has nothing to do with valias stuff. What I meant is that to make it work with the current qmailadmin code requires quite much modifycation.
why PHP ?? If you need to make a complete rewrite, which I would do and actually did, it is much more easier and faster to develop with PHP than C and makes it also much more easier to sysadmins to add their special features if needed. I don't think speed is the critical point when it comes to adding/modifying users. And PHP is propably even faster because you can break the functionality in to smaller pieces. To reset/change password requires just a few lines of PHP code so why should I load a lot of code (qmailadmin binary) which is actually not needed for a simple task like this. And as You said, even PHP is written in C so the underlying code to handle MySQL (mysqlclient) is definitively fast enough for this purpose.... The vpopmail system (which I also wrote from scratch actually) is another story and should be written in C. For comparison, how many times a single account will be modified in a period of time ?? How many POP/IMAP logins and mail deliveries the system need to handle for that account in the same time period ?? So the critical point when it comes to speed is vpopmail, not qmailadmin. Thats what I think. =d0Mi= > Qmailadmin's inability to handle MySQL aliases has little to do with the > programming language it's written in. After all, even PHP is written in C. > > I happen to like that it's written in C. C code means it's nearly as fast as > possible. That means a lot when you have 2000 domains, and users log in > frequently to change their passwords/settings. > > However, I do think it needs a CVS so that programmers can more easily apply > their own code to the project source, and there would be fewer patches > flying around. Apache would have never become the excellent software package > it is today without CVS. Period. > > Jesse Guardiani, Systems Administrator > WingNET Internet Services, > P.O. Box 2605 // Cleveland, TN 37320-2605 > 423-559-LINK (v) 423-559-5145 (f) > http://www.wingnet.net > > We are actively looking for companies that do a lot of long > distance faxing and want to cut their long distance bill by > up to 50%. Contact [EMAIL PROTECTED] for more info. > > > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, November 27, 2002 5:23 PM > Subject: RE: [qmailadmin] qmailadmin on separate apache server > > > > > Hmmm... The nature of qmailadmin requires it to be > installed on on the same maskin where qmail lives. > I have tried several different setups to work my > way a round this problem and some other problems too > and I ended wroting my own system :-) > > ok, I understand that You maybe don't have the time to > do this so here is my workarounds :-) > > 1) share Your mailroot over NFS. > > 2) Run a proxypass from your webserver to qmail machine > so that noone can access apache on your mailserver > directly. > > I think none of these solutions work "out of the box" and > you may meed to do some modification to qmailadmin code. > I cant tell You exactly since I don't have played around with > qmailadmin for over a year or something. Instead, You should > see this as a hint for something that may work. > > > The authors of qmailadmin has made a great job but I think, > and this is MY personal opinion, it is time to make a complete > rewrite and fix some "defects" once and for all. I think the > latest qmailadmin is still unable to handle MySQL alias. > Maybe it's time to move over to PHP+MySQL !!!? > > =d0Mi= > > > I may be wrong, but I'd say that most people just > > throw a web server on the box with vpopmail/qmail > > and run qmailadmin from there. > > > > It kinda messes with the distributed nature of > > your setup, but qmailadmin modifies .qmail files > > and talks to vpopmail via the command line... > > It's gotta have access to those facilities to > > function. > > > > > > On Wednesday 27 November 2002 12:18, John R. > > Hillman wrote: > > > Hello- > > > > > > I have managed to get qmail+vpopmail running > > > properly on one box, with MySQL on another box > > > and Horde/IMP on yet another box (the web > > > server). I would like to use qmailadmin, > > > running on the web server, so that the various > > > hosted domain postmasters can handle all of the > > > administrative tasks like creating/deleting > > > users, changing passwords, etc. Unfortunately, > > > in reading through the INSTALL and README > > > files, searching google.com (groups and www), I > > > can't seem to find any information on using > > > qmailadmin to manage a remote qmail install. > > > Is it possible to accomplish this? Or, does > > > everyone run all of their services on a single > > > box (something I would prefer not to do)? > > > > > > Regards, > > > > > > J > > > > -- > > Jesse Guardiani, Systems Administrator > > WingNET Internet Services, > > P.O. Box 2605 // Cleveland, TN 37320-2605 > > 423-559-LINK (v) 423-559-5145 (f) > > http://www.wingnet.net > > > > We are actively looking for companies that do a > > lot of long > > distance faxing and want to cut their long > > distance bill by > > up to 50%. Contact [EMAIL PROTECTED] for > > more info. > > > > > > > > > > >
