RE: Urgent Help, please!
This perl script creates a new user , it does NOT need to be SUID. Only a script that created a NEW Domain would need to be suid. I have that available if you need it. My apache runs as user vpopmail. I am not a qualified perl programmer, so I offer no security with this script. zack #!/usr/bin/perl -w use CGI ':all'; my $query = new CGI; my $new_user = $query-param('new_user'); my $domain = $query-param('domain'); my $password = $query-param('password'); my $adduser = `/var/vpopmail/bin/vadduser $new_user\@$domain $password`; print header(), start_html(Done.), end_html(); -Original Message- From: The Guyver [mailto:[EMAIL PROTECTED]] Sent: Thursday, September 20, 2001 11:30 AM To: [EMAIL PROTECTED] Subject: Urgent Help, please! Hello there, I'm in a desperate need to write a PHP script that creates a new mailbox with vpopmail 4.10.35 I've written everything correctly but when I use exec or system I always end up with this error: Error: Unable to chdir to vpopmail/domains directory please help me it's very urgent if anybody has a clue I'll appreciate so much. Guyver
domains / 0 directory???
I just got vpopmail-4.10.30 and compiled and installed with ./configure --enable-roaming-users=y --enable-tcpserver-file=/var/vpopmail/etc/tcp.smtp --enable-tcprules-prog=/usr/local/bin/t cprules --enable-default-domain=dnsfirm.com --enable-log-name=vpopmail --enable-logging=yv --enable-relay-clear-minute s=180 I then recompiled vpopmail.pm and I HAD TO REMOVE the old version, a make install did not overwrite the current vpopmail.pm files on the system. Anyways, now that I have everything upto date and working, when I add a new user using either the vpopmail.pm or from the command line using /var/vpopmail/vadddomain the new domain ends up under /var/vpopmail/domains/0/domainname Anyone else experiencing this? +testtest24.com-:testtest24.com:89:89:/var/vpopmail/domains/0/testtest24.com :-:: +testtest25.com-:testtest25.com:89:89:/var/vpopmail/domains/0/testtest25.com :-:: +testtest26.com-:testtest26.com:89:89:/var/vpopmail/domains/0/testtest26.com :-:: +testtest30.com-:testtest30.com:89:89:/var/vpopmail/domains/0/testtest30.com :-:: +testtest31.com-:testtest31.com:89:89:/var/vpopmail/domains/0/testtest31.com :-:: +testtest50.com-:testtest50.com:89:89:/var/vpopmail/domains/0/testtest50.com :-:: . Thanks zack
REQ for enlightenment.
Maybe I am going about this all wrong. I work for a company that has about 30 ASP sites running on Windows 2000 with Coldfusion and a MS SQL backend. They want to offer email hosting accounts to customers and allow the customers to transfer domains to one of the ASP services. Unfortunately everything MUST be done through coldfusion, that's just the company policy. Since I own the domain popadmin.com and have been working on a service similar to critical path I recommended using qmail with the vpopmail package. So I setup qmail with the vpopmail package and configured apache to just accept connections from a private IP for vpopmail managment. Then the coldfusion developers can just send an http request that can be processed by a small perl script which then calls the vpopmail functions or in this case the vpopmail.pm perl module. Can anyone recommend a better way of doing this? Thanks zack
Re: REQ for help: vcdb bug breaking format of users assign and directory structure using vpopmail.pm
The people on this list are wonderful. I did not rebuild the vpopmail.pm module after installing the latest vpopmail. I just went ahead and rebuilt vpopmail.pm based on Sean's recommendation and sure enough everything is working as it should now. Thanks zack - Original Message - From: Sean P. Scanlon [EMAIL PROTECTED] To: Zachary Buckholz [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, July 15, 2001 5:54 PM Subject: Re: REQ for help: vcdb bug breaking format of users assign and directory structure using vpopmail.pm On Sun, Jul 15, 2001 at 02:28:16PM -0700, Zachary Buckholz wrote: I went ahead and got the new development version and after some compilation problems I got it compiled but this is still an existing issue. When adding a domain using vpopmail.pm the assign file gets corrupted. After building a new version of vpopmail, I would suggest re-installing vpopmail.pm did you try that? -- - Sean P. Scanlon perl -e 'print pack(h*, 3707370426c6575646f647e2e65647), \n' -