Thank you very much. Unfortunately, we can't use Apple's proprietary code in our distribution.
I have been working with another individual in getting PAM to work with Mac OS X. He reports that imapd will build if you add CHECKPW=pam and BASELDFLAGS=-lpam to the osx section of imap-????/src/osdep/unix/Makefile, and edit ckp_pam.c so that it uses <pam/pam_appl.h> instead of <security/pam_appl.h>. There's still problems getting it to work; I suspect it's a problem in his /etc/pam.d/imap file but I don't know what. If it's possible to get PAM working, this would be preferable. Standard interfaces are always better. By the way, is there any way for you (and the rest of the Mac OS X user community) to influence Apple to use the standard /usr/include/security for the PAM includes instead of its non-standard /usr/include/pam? NeXT was a nightmare with its non-standard include directories, and I'd hate to see Mac OS X go down the same path. Thanks. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
