Re: auth_imap courier-imap 4.x

Jimmy Brake <[email protected]>
Newsgroups gmane.mail.qmail.ldap
Message-ID <[email protected]>
Hi Leandro,

You can configure courier imap 4.6 to work.

full article

http://store.dwalliance.com/news/view_article.html?article_id=07249ce80822c22a3e55ce546fd737d2

apt-get install courier-pop courier-authdaemon courier-imap
courier-authlib-ldap

Then update /etc/courier/authdaemonrc

authmodulelist="authldap"

Then update /etc/courier/authldap

LDAP_URI ldap://yourldapserver

LDAP_PORT 389

LDAP_BASEDN dc=yourfoo,dc=com

LDAP_BINDDN cn=Manager,dc=yourfoo,dc=com

LDAP_BINDPW yourpass

LDAP_TIMEOUT 5

LDAP_AUTHBIND 0

LDAP_MAIL mail

LDAP_GLOB_UID vmail

LDAP_GLOB_GID vmail

LDAP_HOMEDIR yourldapfoomaildirpath

LDAP_MAILDIR

LDAP_MAILDIRQUOTA mailQuotaSize

LDAP_FULLNAME cn

LDAP_CRYPTPW userPassword

LDAP_AUXOPTIONS mailhost=mailhost

I use perdition as my imap / pop proxy .. we only use it because of
some legacy reasons but you can get courier to pass/proxy the
connection.

Jimmy

Leandro wrote:

On my slackware 9.1x86 courier-imap 2.2.1 works ok with
auth_imap.

I've read that courier-imap 4.x changed the authentication way, so I
can't use auth_imap no longer.

I gave up trying to configure courier-imap 4.6.0 on my slackware 13.0
x86_64 to authenticate with my ldap db.

I think courier-imap 3.x could be the solution.

Does anybody know where I can download sources of courier-imap 3.0.8 ?
(sourceforge seems to remove 3.x releases from download)

Does anybody know if courier-imap 3.0.8 works on x86_64 ?

(I couldn't compile courier-imap 2.x on a x86_64 machine)

Does anybody know how to authenticate courier-imap 4.x ? (using
ldapserver from qmail-ldap or not)

Thanks in advance.

Leandro.

__________________________________________________

Correo Yahoo!

Espacio para todos tus mensajes, antivirus y antispam ¡gratis! ¡Abrí tu
cuenta ya! - http://correo.yahoo.com.ar
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.