ERL5LIB=/private/cyrus/lib/site_perl
export PERL5LIB
This fixed it, and all is happy. I would suspect you have the same
issue with Red Hat. (I had installed Cyrus under FreeBSD, and I didn't
have to add these lines.)
--
Gardiner Leverett [EMAIL PRO
* If we see any we don't like, reject the string.
> */
> sawalpha = 0;
> for(p = retbuf; *p; p++) {
> switch (allowedchars[*(unsigned char*) p]) {
> case 0:
> return NULL;
>
> case 2:
> sawalpha
Gardiner Leverett wrote:
> The problem is this:
> On the new machine, a user mailbox is "foobar" for example.
> The user connects (through the client) as "FOOBAR". SASL
> authenticates the user fine, but the user can't see the INBOX
> or any other f
something in the Cyrus code that I can turn off or
turn on to recognize an connection from "FOOBAR" to the
mailbox "foobar" as the same?
--
Gardiner Leverett [EMAIL PROTECTED]
Merit Network, Inc. Phone: 7
paul dekkers wrote:
>
> Hi,
>
> I built/installed OpenLDAP first - the test.c file I created myself
> could be compiled too, so the configure script should be able too.
>
> I assume otp, kerberos, digest and md5 do not stand in the way for the
> LDAP support to built correctly?
Not as far as I
Rob Siemborski wrote:
>
> On Tue, 15 Oct 2002, Gardiner Leverett wrote:
>
> > Great! I'll go try that first. Is there any documentation for the saslauth
> > db file? According to the web docs included with the source, it says to
> > check the man page for sas
Rob Siemborski wrote:
>
> On Tue, 15 Oct 2002, Gardiner Leverett wrote:
>
> > After fussing around with the make files so that cyrus-sasl would
> > actually include the pam library, cyrus still doesn't have the library
> > on compile, and trying to test the ser
hat to do next. Trying
to telnet to the imap port produces no result. The items
are not in inetd.conf (as I did get one of those
imapd: could not getenv(CCYRUS_SERVICE) errors
in the log as well).
Any help would be appreciated!
--
Gardiner Leverett
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
ett
> > 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
> > section :)
> &g
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
11 matches
Mail list logo
