OK. Never thought to look in log/maillog. It's informative here: vpopmail user not found ...
Bob suggested a permission problem with apache. I'll try setting up suid and getting back. I think we're on the right track. On Sunday, October 19, 2014 12:36 PM, Darek M. <da...@nyi.net> wrote: If you have the compile directory from the old setup, I would look at 'config.log' for the configure script arguments. Maybe you can post your configure command for the current qmailadmin install. Vpopmail should also have its own logfile. It's usually very informative. Anything in /var/log/maillog ? On 10/19/2014 3:31 PM, francis drake wrote: > Thanks for getting back to me, Derek. > > It's a .gz install. I'm using daemontools and checked all the qmail logs. > I'm not getting any logs from pop3d. I'll have to look into that. > > > > > On Sunday, October 19, 2014 12:09 PM, "da...@nyi.net" <da...@nyi.net> wrote: > How did you install, from source or RPMs? IIRC when I last dealt with > qmailadmin/vpopmail, qmailadmin had to be told about vpopmail with a > flag. As for logging in, you should be able to log in as any user that > vpopmail is aware of. > > Also, check your logs. Location depends on how you're running qmail > (daemontools, etc). > > > > > > On 19.10.2014 14:28, francis drake wrote: >> Hi all, >> >> After more than 10 years my qmail, vpopmail, and qmailadmin setup >> died catastrophicly. qmailadmin was the core part of administering >> everything. >> >> I now have a new install of that setup. Mail delivery works and I can >> retrieve email from the postmaster and user accounts. >> >> However, loggin into qmailadmin's postmaster account using >> postmaster >> my.domain >> password >> results in "Invalid Login". I also tried "postmaster@my.domain" but >> that doesn't work either. >> >> I reinstalled both vpopmail and qmailadmin but that didn't fix the >> problem. Also tried both 1.2.15 and 1.2.16. >> >> I checked the mail archives and even poked around in qmailadmin.c but >> am pretty lost when it comes to c programming. >> >> The o/s is fedora 20. >> >> Any help with this will be greatly appreciated, especially tips on >> how to debug this situation (didn't have much luck trying various >> printf instructions in the source). >> >> Looking forward to hearing from you, >> Mike Wright >> >> > > > > > !DSPAM:544413ef26512142328780!
