Hello all, I have a server running a minimal install of 9.1 plus a few extra packages needs to run some apps. One of those apps is Courier. After it was in production for a while, we started getting complaints that some users were getting intermittant login failures. I checked and the other two servers that run Courier were working fine (both RedHat9), but the Suse box was failing the authentication. After pulling my hair out for a couple hours, I noticed that the crypted passwords for the problem users all start with $1 and the ones that work do not. Upon further investigation, I found that the problem passwords were generated by a script on an old Slackware box (kernel 2.2). The good passwords were generated by a script on another RedHat9 box. I don't know a whole lot about encryption algorithms, but I'm guessing that the Slackware box produced passwords using an old algorithm that the RedHat box still had support for, but Suse9.1 does not (or at least does not with the minimal install that I have). It appears that the userdbpw binary for Courier is linked against /lib/libcrypt.so.1 which belongs to glibc. I have: RedHat9: glibc-2.3.2-27.9 Suse9.1: glibc-2.3.3-97 Does anyone have any ideas how I can get Suse to read the old passwords? Am I just missing a package or two? Thanks! -- Dennis Skinner Systems Administrator BlueFrog Internet http://www.bluefrog.com "Autumn is a second spring when every leaf is a flower. - Albert Camus"