On Sun, 30 Jul 2006, Andrew J Herbert wrote:
"osdep.c", line 147.13: 1506-068 (W) Operation between types
"int(*)(int,struct pam_message**,struct pam_response**,void*)" and
"int(*)(int,const struct pam_message**,struct pam_response**,void*)" is not
allowed.
Ugh. IBM bites us again.
The conv pointer prototype on Linux, BSD, and Solaris systems all the
second argument as a const struct pam_message**. Apparently, someone at
IBM decided that it shouldn't be a const.
Nevertheless, that diagnostic is a warning, and the compiler should
generate the correct object code.
These were all imap-2004g, all resulted in a binary which appeared to run,
but only the std-build would authenticate. The pam.conf file was left as
it came from AIX with an imap entry.
This sounds like a stupid question, but have you thoroughly analyzed the
PAM configuration to make sure that it is set up for IMAP? This problem
may be a PAM configuration problem instead of an imapd problem.
I don't know anything about pam.conf (or what IBM may have done with it),
but typically there is an /etc/pam.d/imap file which contains more or less
the same contents as what you have for ftp, rsh, etc.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
