Cyrus IMAPd 2.2.3 Released

[Igor Brezac]

On Fri, 16 Jan 2004 dimon at intellinetinc.com wrote:

>
> > The actual code did not change, just the Berkeley detection did.  If you
> > remove db 4.1.25 from your system, the sasl configure script should find
> > 4.2.52 (Do not forget to apply a patch from the sleepycat site:
> > http://www.sleepycat.com/update/4.2.52/patch.4.2.52.html)
> >
> I'm installing it from FreeBSD ports collection, and there is no option in
> Makefile to compile it with BDB 4.2. I can hack it to recognize
> WITH_BDB_VER=42, so this way it will add these options to configure script: --
> with-bdb=db42 --with-bdb-incdir=/usr/local/include/db42
> Is that what needs to be done?
>

I am not familiar with FreeBSD.  My guess is that this is not going to
work.

>
> > Hmm, I not sure what that is.  Can you give us backtrace and your
> > saslauthd startup cmd?
> >
> What is that backtrace? The startup command is the saslauthd.sh script that
> comes as a part of FreeBSD cyrus-sasl2 port:
> [root at localhost cyrus-sasl2]# ps ax|grep sasl
>  2442  ??  Is     0:00.51 /usr/local/sbin/saslauthd -a pam
>  2443  ??  I      0:00.50 /usr/local/sbin/saslauthd -a pam
>  2444  ??  I      0:00.49 /usr/local/sbin/saslauthd -a pam
>  2445  ??  I      0:00.49 /usr/local/sbin/saslauthd -a pam
>  2446  ??  I      0:00.49 /usr/local/sbin/saslauthd -a pam
>

Auch...  saslauthd/pam is known to be unreliable, furthermore you cannot
use saslauthd/pam combination for fully qualified userids (user at domain)
because libsasl (2.1.17+) ignores the realm (domain) portion.  ;(

-- 
Igor