> Off hand, I'd guess it's a permission problem. Check the modes on all
> the parent directories of the Maildir. Compare them with the system
> that works right.
Here is what happens when I do this manually --
[me@myhost me]$ telnet localhost 110
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
+OK <[EMAIL PROTECTED]>
user me
+OK
pass mypassword
shell-init: could not get current directory
+OK
list
+OK
1 601
quit
+OK
Connection closed by foreign host.
If I am reading the `list` correctly, that is
the one message that I have in my Maildirs,
which is 601 bytes long (verified using ls -l)
and is actually stored in the "curr" directory
of a folder (Maildir/.folder/curr has a file
which is 601 bytes long), so it doesn't appear
to be a permissions problem at that end.
When running the test line from checkpassword
as a normal user, I get "authorization failed".
If I run it as root, I can log in correctly.
The test command is:
/var/qmail/bin/qmail-popup host /bin/checkpassword pwd
I get the impression there is a permissions
problem which prohibits login even on a properly
configured server because the two different
servers I have also fail running the above
command, but the one (RH6.0) complains about
not being able to write to a pipe, and the
other (RH5.1) complains about not being able
to write to the filter files for temporary
relaying ala open-smtpd mods and then complains
about tcpmakectl not being able to write to
temporary output. Both of these systems work
during normal operation, however.
Notice on my non-working system it seems to
not even get far enough to complain about
not being able to write to the output pipe.
Any ideas where I should look for these
permissions problems? What other applications
are needed to login?
Thanks,
~Patrick
