will ldap auth and directory services be included in a future version of
this imap implementation?
thanks.
-marlon
At 07:05 PM 10/26/99 -0400, Sam wrote:
>Courier-IMAP provides IMAP access to Maildirs. Written from scratch, it
>weighs in at 1/5th the size of UW-IMAP, despite a reasonably complete
>IMAP4rev1 implementation.
>
>There might be some problems with vchkpw support in this first version,
>but everything else is functional. Strict implementation of RFC 2060
>(IMAP4rev1) means that pretty much every IMAP client I tested was broken
>in some way - even Pine (!), although Pine's IMAP implementation was the
>best one I've looked at. Netscape Communicator's IMAP client also works,
>although until someone at Netscape figures out that there is no such thing
>as a negative message sequence number, checking for new mail and copying
>messages between folders may not work very well. Microsoft Outlook works
>more or less ok, but only because I relented and accomodated its bugs that
>made folder creation and deletion a rather annoying experience.
>
> http://www.inter7.com/courierimap/
>
>* Very fast. I opened a folder with 700 msgs for the first time with no
> noticeable delay (on a reasonably fast box).
>
>* Supports /etc/passwd, /etc/shadow, and MD5 passwords. Supports PAM.
> Allegedly supports vchkpw (not tested). Supports userdb (basically a
> GDBM or DB based virtual mailbox database). PAM support basically means
> that any PAM module can be used for authentication.
>
>* Same userdb and maildir driver as maildrop (and sqwebmail).
> Courier-IMAP will see and access sqwebmail's folders.
>
>* Some anti script-kiddie measures - limit on max # of connections, limit
> on max # of connections from the same IP address. Artificial delays for
> bad passwords.
>
>What this means is that you no longer need to hack Pine into reading
>Maildirs. Just run the server on localhost, and tell Pine to use IMAP to
>localhost to read INBOX or file mail into folders.
>
>--
>Sam
