Hallo Randall, Thanks for your answer and informations. Yes you are right I tried without the
--with-pam=pop3 --enable-specialauth options to configure than the poppassd daemon was created successfully. I also could get APOP Auth. get working, the problem was that OE5.x doesn't support APOP. I tried with pegasus mail than it worked also. The pam_ldap auth. I am still searching to get it working. This problem has nothing to do with qpopper, but with config. of ldap.conf and nds settings at the novell ldap servers side. Will see and inform if I have some news here. Thanks Reg, Andreas > Try doing a 'make realclean' and then re-run ./configure, but omit > the '--enable-specialauth' you added before. You usually don't need > to specify this; ./configure generally figures out if it is needed; > specifying it when it isn't needed can cause the error you are seeing. > > > 2) Do I need the the poppassd daemon running to get apop auth. working? > > No, the two are entirely separate. In fact, poppassd won't even > change the apop password (it could be hacked to do so, but you would > really want to run it under TLS). > > > 3) How is the order how qpopper uses the auth. methods or must > > I configure that with ./configure script or with the qpoppers -f option in > > a config > > file. > > > > e.g. what should I configure if I wanted to use apop and/or pam (ldap) as > > auth > > method. or can I use always on method at once e.g. apop or pam (ldap). > > You don't configure this in Qpopper. If a user has an APOP password, > Qpopper requires the user to authenticate using APOP and not any > other mechanism. > > > 4) I assume SSL (--with-openssl) can be used for all auth options. > > Yes, it's independent of authentication. >
