Hi Jeremy,

let me first please you to answer on list so the mails get archived and
might be used for future reference.

On Tue, 10 Dec 2002 14:07:46 -0500
Jeremy Doolin <[EMAIL PROTECTED]> wrote:

>>> I'm having fits getting qmailadmin to authenticate properly.  Here
>>> is my setup:
>>> qmail, vpopmail, autoresponder, ezmlm, apache 2.0, squirrelmail,
>>> courier-imap.
>>> I can authenticate with my virtual user ([EMAIL PROTECTED]) via
>>> squirrelmail, sqwebmail, pop3 and IMAP, but not qmailadmin.  I enter
>>> "postmaster" for the user account, "domain.com" for the domain name
>>> and my password and I continue to get "Invalid User".  Any help with
>>> this would be greatly appreciated.  Thanks.

>> Have a look into system log, maybe vchkpw logs the reason of
>> rejection. Might be it's only your qmailadmin cgi is not properly
>> set SUID and therefore refused to authenticate.

> well, I checked the permissions and it was as follows:
> -rwsr-sr-x  1  vpopmail  vchkpw       99728 Dec 10 10:23 qmailadmin
> upon advising from  a friend, I changed it to 4711, or:
> -rws--x--x
> but it still doesn't work.

chmod 6755 qmailadmin

should be OK.

So you still didn't tell us what's in system log (if vchkpw logs
something about unable to authenticate) and what is maybe in web servers
log about possible errors.

You don't write about your OS, so I don't know if it's Linux or a BSD.
For Linux you could try to attach a strace() process to apache processes
to maybe figure out if and where permission might be denied.

As an example you can use the following as a "template" and adapt it to
your concrete setup:

ps auxwww |grep '[h]ttpd' |awk '{print $2}' >/tmp/pids_of_httpd
while read x; do PIDS="$PIDS -p $x"; done < /tmp/pids_of_httpd
strace -s 512 -o /tmp/qmailadmin.log -fqix $PIDS

Replace '[h]ttpd' with the name of your web server binary. On my Debian
it's 'apache' and therefore '[a]apache', the parethis '[]' around the
first characters make the 'grep' recognize only "the real processes" but
exclude itself from the resulting list.

Now try to log in and after failure have a look in 


if you can figure out the culprit.

You should use this on a web server not to busy with other stuff, else
the log file (/tmp/qmailadmin.log) will be filled with a _lot_ of
useless information for sloving this issue.
If your web server _is_ busy, start a new instance with different
configuration file, bound to, figure it's IPs manually
and 'strace()' this PIDs.

If you're not using Linux you'll have to search for how to apply an
strace() to a running process yourself, unless somebody else on this
list, who uses BSD, can help out. I don't have a single BSD machine here
(yet), so I don't have any clue what's different, but the general
strategie should be very similar.

Reply via email to