sh
UNIX Systems Administrator
Information Technology Services
Vanderbilt University
Office: (615) 322-2156
Cell: (615) 491-4115
-Original Message-
From: Igor Brezac [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 06, 2005 3:58 PM
To: Saltmarsh, Evan M
Cc: info-cyrus@lists.andrew.cmu.edu
Subje
mation Technology Services
Vanderbilt University
Office: (615) 322-2156
Cell: (615) 491-4115
-Original Message-
From: Andrew Morgan [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 06, 2005 3:03 PM
To: Saltmarsh, Evan M
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: IMAP authentication
mation Technology Services
Vanderbilt University
Office: (615) 322-2156
Cell: (615) 491-4115
-Original Message-
From: Andrew Morgan [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 06, 2005 3:03 PM
To: Saltmarsh, Evan M
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: IMAP authentication
Andrew Morgan [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 06, 2005 3:03 PM
To: Saltmarsh, Evan M
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: IMAP authentication via LDAPS
On Thu, 6 Oct 2005, Saltmarsh, Evan M wrote:
> I'm having trouble getting LDAPS to work with cyrus. We've bee
On Thu, 6 Oct 2005, Saltmarsh, Evan M wrote:
I'm having trouble getting LDAPS to work with cyrus. We've been able to
get LDAPS to work using stunnel to encrypt the path, but if we change
the saslauthd.conf file to point to the LDAPS port, we get the following
in our syslog, and it appears the
I’m having trouble getting LDAPS to work with cyrus.
We’ve been able to get LDAPS to work using stunnel to encrypt the path,
but if we change the saslauthd.conf file to point to the LDAPS port, we get the
following in our syslog, and it appears the connection to the LDAP server is
never es