I wanted to include a solution to the problem that
I submited to this list a week ago.
The problem I had was having the Cyrus server
respond at all after building it with the Cyrus-SASL
software. I want it to work with OpenLDAP and
the pam_ldap module so the users do not have to
be in /etc/pa
t; > make all CFLAGS=-O
> >
> > Hope this helps,
> > Lee
> >
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]] On Behalf Of Tarjei Huse
> > Sent: Friday, November 09, 2001 5:26 PM
> > To: Gardiner Lever
om: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Tarjei Huse
> Sent: Friday, November 09, 2001 5:26 PM
> To: Gardiner Leverett
> Cc: [EMAIL PROTECTED]
> Subject: Re: Solaris 7 and Cyrus 2.0.16/LDAP/SASL/PAM
>
> This lookes like the good old SASL-LDAP problem.
Behalf Of Tarjei Huse
Sent: Friday, November 09, 2001 5:26 PM
To: Gardiner Leverett
Cc: [EMAIL PROTECTED]
Subject: Re: Solaris 7 and Cyrus 2.0.16/LDAP/SASL/PAM
This lookes like the good old SASL-LDAP problem. Have you read the FAQ?
Faq: cyrus-utils.sf.net/faq have a special look at the death by 11
This lookes like the good old SASL-LDAP problem. Have you read the FAQ?
Faq: cyrus-utils.sf.net/faq have a special look at the death by 11 section :)
Hope this helps.
Tarjei
Gardiner Leverett wrote:
>
> I have a rather complicated load I'm trying to do. I've been going
> through the archives
I have a rather complicated load I'm trying to do. I've been going
through the archives without any answers.
I have a server running Solaris 2.7, and I'm trying to build Cyrus 2.0.16
with SASL 1.5.24, OpendLDAP 2.0.18, and pam_ldap 1.33.
I can't even tell if any of this is working as the im
