On Sat, Feb 09, 2002 at 01:05:41PM -0500, Daniel Yu wrote:
> Here is what we have to give you an example.
> OpenLDAP as backend directory.
> Both Cryus-SASL.1.5.27 and 2.1.1 are installed. Cyrus-SASL-1.5.27 uses
> PAM to authenticate with LDAP. 2.1.1 uses saslauthd to authenticate with
> LDAP via
> On Fri, 01 Feb 2002 01:00:22 -0800,
> Erik Steffl <[EMAIL PROTECTED]> (es) writes:
es> Q: how do other people cope with troubleshooting problems of cyrus
es> (and mainly sieve)? Are there any tools that I am not aware of? Is it
es> getting better (the above is with older cyrus/sieve (
> Unless you have a need for the non-plaintext mechanisms, try removing
> these plugins. Sieveshell will try to use the "best" (highest SSF)
> mechanism that it finds. If you only have PLAIN and/or LOGIN installed,
> it will have no choice but to use one of these, which should then use
> your P
Have you tried all the steps in the faq @ cyrus-info.sf.net ? I know it's not to
easy to install cyrus on r.h 7.1 (I'm running it myself),
> HOWEVER. On the first run of cyradm from a fresh install, it complains
> about Shell.pm not being in the path. So I created Cyrus/IMAP in my perl
> path
Justin Wood wrote:
>
> I recently installed cyrus-imapd 2.0.16 w/ cyrus-sasl 1.5.27 on FreeBSD
> 4.5-RELEASE (from the ports tree). I managed to get imapd auth working
> just fine, but when I try to install a sieve script using installsieve,
> I get the following messages in syslog:
>
> Feb
Well, it has been some time since I last posted here :) RL has been a bit
busy.
Anyway, SASLv2 made it to Debian (it is not 100% functional right now, but I
trust the maintainer will fix that shortly; If he doesn't, I will), and that
means I can upload Cyrus IMAPd version 2.1.1 (from CVS) to Debi
