dovecot - Sep 2005 - (no subject)

I am trying to get away from courier imap because it is flaky the way it
uses FAM (or gamin in my case), and the developers seem to have a chip on
their collective shoulder, and it is too complex. I found dovecot because
it is ships with CentOS 4 (ie Red Hat Enterprise 4). It looks like just
what I need: simple, fast. But I can't use it! I can't authenticate. If
any of these statements were untrue, I would use it happily:

o it doesn't support simple bind authentication against LDAP
o I don't want to make passwords readable, and this version (0.99.14)
doesn't support SSHA anyway
o it won't talk to the saslauthd I already have configured
o I can't find how to implement a new auth module for dovecot

I am wondering why, in the quest to fill a niche with a simple, fast,
secure IMAP server, the authors felt the need to re-implement a robust and
well-tested infrastructure (saslauthd) with a less-featureful and untested
one?

On Thu, 1 Sep 2005, Phillip Needham wrote:
> I am trying to get away from courier imap because it is flaky the way it
> uses FAM (or gamin in my case), and the developers seem to have a chip on
> their collective shoulder, and it is too complex. I found dovecot because
> it is ships with CentOS 4 (ie Red Hat Enterprise 4). It looks like just
> what I need: simple, fast. But I can't use it! I can't
authenticate. If
> any of these statements were untrue, I would use it happily:
>
> o it doesn't support simple bind authentication against LDAP
> o I don't want to make passwords readable, and this version (0.99.14)
> doesn't support SSHA anyway
> o it won't talk to the saslauthd I already have configured
> o I can't find how to implement a new auth module for dovecot
Just use PAM.

-- 
Ignacio Vazquez-Abrams