Michael's answer that you need to use "make oxp" instead of "make osx" on
Tiger is correct. Apple broke/removed the traditional UNIX means of
authentication, thus making use of PAM mandatory.
However, his answer was incomplete, since you are also confused about what
LOGINDISABLED means. A server that utters LOGINDISABLED when you connect
to port 143 is
(1) compliant with the IMAP specification
(2) behaving as-expected and correctly
Similarly, a server which does not do so is non-compliant and not behaving
correctly.
Simply stated, you can NOT telnet to a modern, compliant, IMAP server and
log in to it. The LOGIN command is deprecated in general, and is
prohibited on unencrypted (not protected by SSL or TLS) connections.
Details are in RFC 3501 (search for STARTTLS, LOGINDISABLED, and
especially the entire Security Considerations section)
It is possible to build UW imapd to be a non-compliant, incorrect server
that allows the LOGIN command on unencrypted connections. This is NOT
encouraged, but is available for those sites which must have that
capability.
Details are in docs/BUILD and docs/SSLBUILD. SSLBUILD will also describe
certificates. As for where UW imapd expects certificates to be on a
particular system, the easiest way is to look at c-client/OSCFLAGS after
building and look at the definitions of SSL_CERT_DIRECTORY and
SSL_KEY_DIRECTORY.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
