Re: Make file blues
Ken == Ken Jones [EMAIL PROTECTED] writes: Ken Besides it looking like the chown happens before the install Ken of qmailadmin binary, what is the problem? What doesn't Ken work? The binary will have default ownership and permissions (at least on my system) [354]# ls -l qmailadmin -rwxr-xr-x1 root root 379879 Nov 28 01:46 qmailadmin [355]# chown vpopmail qmailadmin [356]# chgrp vchkpw qmailadmin [357]# chmod u+s,g+s qmailadmin [358]# ls -l qmailadmin -rwsr-sr-x1 vpopmail vchkpw 379879 Nov 28 01:46 qmailadmin [359]# install -c -s qmailadmin /home/httpd/cgi-bin/qmailadmin [360]# ls -l qmailadmin /home/httpd/cgi-bin/qmailadmin -rwxr-xr-x1 root root 168148 Nov 28 10:10 /home/httpd/cgi-bin/qmailadmin -rwsr-sr-x1 vpopmail vchkpw 379879 Nov 28 01:46 qmailadmin [361]# Ken On Wed, 2001-11-28 at 01:02, Brent B.Powers wrote: I don't know why I seem to be the only one crying about these odd problems. Here's the output from a 'make install-strip': # make install-strip make AM_INSTALL_PROGRAM_FLAGS=-s install make[1]: Entering directory `/usr/src/qmail/qmailadmin-1.0' make[2]: Entering directory `/usr/src/qmail/qmailadmin-1.0' make[3]: Entering directory `/usr/src/qmail/qmailadmin-1.0' /bin/sh ./mkinstalldirs /home/httpd/cgi-bin chown vpopmail /home/httpd/cgi-bin/qmailadmin chgrp vchkpw /home/httpd/cgi-bin/qmailadmin chmod u+s,g+s /home/httpd/cgi-bin/qmailadmin /bin/sh ./mkinstalldirs /usr/local/share/qmailadmin/ /usr/bin/install -c -s qmailadmin /home/httpd/cgi-bin/qmailadmin /bin/sh ./mkinstalldirs /usr/local/share/qmailadmin//html cp -R html/* /usr/local/share/qmailadmin//html /bin/sh ./mkinstalldirs /home/httpd/html/images /bin/sh ./mkinstalldirs /home/httpd/html/images/qmailadmin cp -R images/* /home/httpd/html/images/qmailadmin make[3]: Leaving directory `/usr/src/qmail/qmailadmin-1.0' make[2]: Leaving directory `/usr/src/qmail/qmailadmin-1.0' make[1]: Leaving directory `/usr/src/qmail/qmailadmin-1.0' So, what's the problem? the chown, chgrp and chown is done _before_ the install. I've no idea how standard install is, but how about replacing: chown vpopmail /home/httpd/cgi-bin/qmailadmin chgrp vchkpw /home/httpd/cgi-bin/qmailadmin chmod u+s,g+s /home/httpd/cgi-bin/qmailadmin /bin/sh ./mkinstalldirs /usr/local/share/qmailadmin/ /usr/bin/install -c -s qmailadmin /home/httpd/cgi-bin/qmailadmin with: /bin/sh ./mkinstalldirs /usr/local/share/qmailadmin/ /usr/bin/install -g vchkpw -o vpopmail -m 6755 -c -s qmailadmin /home/httpd/cgi-bin/qmailadmin I think that will do it. Works on linux and freebsd
Make file blues
I don't know why I seem to be the only one crying about these odd problems. Here's the output from a 'make install-strip': # make install-strip make AM_INSTALL_PROGRAM_FLAGS=-s install make[1]: Entering directory `/usr/src/qmail/qmailadmin-1.0' make[2]: Entering directory `/usr/src/qmail/qmailadmin-1.0' make[3]: Entering directory `/usr/src/qmail/qmailadmin-1.0' /bin/sh ./mkinstalldirs /home/httpd/cgi-bin chown vpopmail /home/httpd/cgi-bin/qmailadmin chgrp vchkpw /home/httpd/cgi-bin/qmailadmin chmod u+s,g+s /home/httpd/cgi-bin/qmailadmin /bin/sh ./mkinstalldirs /usr/local/share/qmailadmin/ /usr/bin/install -c -s qmailadmin /home/httpd/cgi-bin/qmailadmin /bin/sh ./mkinstalldirs /usr/local/share/qmailadmin//html cp -R html/* /usr/local/share/qmailadmin//html /bin/sh ./mkinstalldirs /home/httpd/html/images /bin/sh ./mkinstalldirs /home/httpd/html/images/qmailadmin cp -R images/*/home/httpd/html/images/qmailadmin make[3]: Leaving directory `/usr/src/qmail/qmailadmin-1.0' make[2]: Leaving directory `/usr/src/qmail/qmailadmin-1.0' make[1]: Leaving directory `/usr/src/qmail/qmailadmin-1.0' So, what's the problem? the chown, chgrp and chown is done _before_ the install. I've no idea how standard install is, but how about replacing: chown vpopmail /home/httpd/cgi-bin/qmailadmin chgrp vchkpw /home/httpd/cgi-bin/qmailadmin chmod u+s,g+s /home/httpd/cgi-bin/qmailadmin /bin/sh ./mkinstalldirs /usr/local/share/qmailadmin/ /usr/bin/install -c -s qmailadmin /home/httpd/cgi-bin/qmailadmin with: /bin/sh ./mkinstalldirs /usr/local/share/qmailadmin/ /usr/bin/install -g vchkpw -o vpopmail -m 6755 -c -s qmailadmin /home/httpd/cgi-bin/qmailadmin I think that will do it. Works on linux and freebsd
Re:qmailadmin 1.0 canidate
Ken == Ken Jones [EMAIL PROTECTED] writes: Ken The final qmailadmin 1.0 canidate is available now Ken http://www.inter7.com/devel/qmailadmin-1.0.tar.gz Ken There are no known problems with this release. If no problems Ken are reported in the next two days we will release this Ken version as 1.0 to work with vpopmail-5.0. Ummm, little problems: The following patch is still required: qmailadmin.patch Description: Binary data And, as others have mentioned... If you don't make as root, you won't be able to link up with the standard vpopmail libraries. On the other hand, if you install as root, the permissions and owner for qmailadmin won't be set properly. If anyone wishes, I can gen up a patch to make the makefile work only as root
Upgrade FAQ and a bug in 0.91
Upgraded to .90 with vpopmail 5.0, then patched up to .91 1.) My qmail admin setup is pretty screwed up right now, but I believe that if login fails, no error message is given, just a straight return to the login screen. The attached patch is trivial and fixes it (StatusMessage not being set before use). qmailadmin.patch 2.) I'm convinced this is a FAQ, and it irritates me that I can't find the solution, but I upgraded to vpopmail 5.0, and then grabbed .90 and patched up to .91. I can no longer log in (Invalid Login). I have a.) Thrown in debug messages to know that it blows out at the patch above (vauth_passwd fails and returns NULL) b.) Ensured that everything in sight is owned by vpopmail in group vchkpw (having configured with --enable-vopuser=vpopmail)). 3.) Turned on very verbose logging in vpopmail and seen that I am getting pop login's working properly. 4.) Whimpered and cried. 5.) Verified that making qmailadmin sticky doesn't help. 6.) Reset the password on the postmaster account, and tried again. It irritates me that I _know_ I've seen this problem before, but can not recall the solution. So, Is there a FAQ list? I'll write this one up (I have searched the archives, but couldn't find) if it's not there and I just can't find it. 3.) [OT, sortof] The whole purpose of this was to get ready to install Courier-IMAP. I've not found a howto that is specific to vpopmail and qmailadmin. Does anyone know of one? Cheers
server blockage
Mea culpa. I just found that bl.spamcop.net was blocking all of 209.218.8.2 :( If anyone sent me anything requiring a response, please resend to me directly. Cheers.
FAQ's
I know this is a faq. I know it's regularly asked. I also know that I've solved it before with earlier versions. That, however, doesn't help. I just upgraded vpopmail to 5.0, and qmailadmin to .90 with the .91 patches. I can no longer log in. Configure was done with ./configure --enable-vpopuser=vpopmail /home/httpd/cgi-bin/qmailadmin is 755 and owned by vpopmail.vchkpw everything within /home/vpopmail is owned by vpopmail.vchkpw Tell you what: If I can get this working on Sunday, I'll start working on a FAQ...
qmailadmin unable to login
It's good to see that I'm not entirely alone in this one. I have been unable to login to my server via qmailadmin, from any machine, and from any browser I have available to me (netscape, lynx, and opera). 1.) Installation: summary qmail-1.03, qmailadmin-0.45, vpopmail-4.9.8-1 I have installed (pretty much default) qmail-1.03, vpopmail-4.9.8-1, vqadmin-1.6, ucspi-tcp-0.88, autorespond-1.0.0, daemontools-0.70, ezmlm-0.53. The only one of these with significant arguments to configure was vpopmail with a configure command of ./configure --enable-default-domain-name=B2Pi.com --enable-ip-alias-domains=y --enable-logging=e --enable-roaming-users=y qmail was setup basically according to Life with qmail. I am able to send and receive mail via qmail. I am able to create virtual domains via vpopmail. I am even able to use vqadmin to it's (apparent) full extent. Furthermore, I have telnet'd into the popserver as postmaster and as a regular use, and have sucessfully retrieved mail (well, OK, postmaster had no mail, but I would have gotten it if it had been there. 2.) Logs at 1:43, I attempted to login to qmailadmin from 192.168.1.1. The http access_log shows: 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /cgi-bin/qmailadmin HTTP/1.0 200 5532 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /images/qmailadmin/uppermiddle1.gif HTTP/1.0 200 2773 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /images/qmailadmin/upperleft.gif HTTP/1.0 200 17413 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /images/qmailadmin/upperright.gif HTTP/1.0 200 293 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /images/qmailadmin/middleright1.gif HTTP/1.0 200 60 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /images/qmailadmin/pixel.gif HTTP/1.0 200 49 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /images/qmailadmin/uppermiddle1.gif HTTP/1.0 200 2773 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /images/qmailadmin/upperright.gif HTTP/1.0 200 293 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /images/qmailadmin/upperleft.gif HTTP/1.0 200 17413 192.168.1.1 - - [24/May/2001:01:43:33 -0400] GET /images/qmailadmin/middleleft1.gif HTTP/1.0 200 14854 192.168.1.1 - - [24/May/2001:01:43:34 -0400] GET /images/qmailadmin/lowerleft.gif HTTP/1.0 200 333 192.168.1.1 - - [24/May/2001:01:43:34 -0400] GET /images/qmailadmin/lowerright.gif HTTP/1.0 200 228 192.168.1.1 - - [24/May/2001:01:43:34 -0400] GET /images/qmailadmin/middleleft2.gif HTTP/1.0 200 74 192.168.1.1 - - [24/May/2001:01:43:34 -0400] GET /images/qmailadmin/middlelogin.gif HTTP/1.0 200 1051 192.168.1.1 - - [24/May/2001:01:43:34 -0400] GET /images/qmailadmin/lowermiddle.gif HTTP/1.0 200 62 192.168.1.1 - - [24/May/2001:01:43:34 -0400] GET /images/qmailadmin/lowermiddle.gif HTTP/1.0 200 62 192.168.1.1 - - [24/May/2001:01:43:34 -0400] GET /images/qmailadmin/middleleft1.gif HTTP/1.0 200 14854 192.168.1.1 - - [24/May/2001:01:43:36 -0400] GET /images/qmailadmin/pixel.gif HTTP/1.0 200 49 192.168.1.1 - - [24/May/2001:01:43:46 -0400] POST /cgi-bin/qmailadmin HTTP/1.0 200 That last one really does bother me. Unless I'm mistaken, it shows a POST executing successfully (return code 200). Nevertheless, I get an Invalid Login message :( There does not appear to be anything relevant in the qmail logs (timestamps of last entry are over 90 minutes previous to the above) There is also nothing significant in the message log. Again, the only things extant are from over 30 minutes previous. Three things come to mind: 1.) Is it possible that this just doesn't work on a linux-sparc system (Answer: Probably not. vpopmail doesn't seem to have any problem)? 2.) how does one debug vchkpw to find out just what is going on? 3.) Why am I not getting a better log telling me why the permissions are bad and on what files? BTW, what I've tried so far is removing almost my entire qmail installation, and starting over, as well as searching docs and mail lists. Anyone have any ideas?
Re:qmailadmin unable to login (addendum)
Just so that no one asks the question, the relevant section of httpd.conf is Directory /home/httpd/cgi-bin Options ExecCGI /Directory and the executable itself is: (Sophie)/home/httpd/cgi-bin[5]%ls -l total 124 -rwxr-xr-x1 root root 118360 May 24 00:32 qmailadmin drwxr-xr-x3 vpopmail vchkpw 4096 May 24 00:17 vqadmin (Sophie)/home/httpd/cgi-bin[6]% Cheers again.
