Hi all. I have seen questions about this error asked a few times and have
also tried to get help with it as well...
Today I finally took the time to step through the code and have found why
the error occured in my case - I am not certain whether or not this will
apply to (m)any others. To the explanation:
My problem was created b/c I setup a test system w/ all the pieces (qmail,
vpopmail, mysql, qmailadmin, etc...). All worked fine. Then I ripped out the
system and rebuilt it - but the mysql database stayed (actually it moved
servers, but that's a moot point). So, when I got the qmail system back up
and running, my postmaster account was still in the database and still
authenticated just fine, even in qmailadmin - I tested this by trying the
right password (which gave me the 'bad file' error) and a wrong password
(which correctly told me I could not be authenticated).
BUT, apparently when I re-created my domain, vpopmail puked on adding the
account in the database (it already existed) and therefore never created the
'/vpopmail/domains/mydomain.com/postmaster' account directory... well, right
after you authenticate in qmailadmin, it writes what I can only assume is a
lock file (it contains the user's ip address) in
'/vpopmail/domains/mydomain.com/postmaster/Maildir'. If it can't, it simply
returns 'bad file'
My 'solution' was to simply send [EMAIL PROTECTED] an email - qmail
then created the folders correctly for me and I was able to login. I'm sure
you could create the directory manually as well, I just felt safer letting
qmail do it. Hope this helps someone!!
Jesse
