[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Getting IMAP to work with OpenLDAP



Am Freitag, 11. April 2003 08:01 schrieb Vishal Khanna:
> Martin
> <snip>
>
> > cyrus does no use imap. It is not designed to do that. cyrus uses sasl to
                      |-- Ah sory, typo, must be ldap

> > authenticate and sasl can be configured to use pam or ldap.
>
> It does at least that is what it says..
>
> http://www.linuxgeek.net/ispman/x331.html
>
> Check this out it can be done..

Yes, it says, sasl (from cyrus too) can do authentification against ldap via 
pam, not cyrus-imap. so to be precise, cyrus-imap uses cyrus-sasl to 
authenticate.

>
>
>
> <snip>
>
> > that has nothing to do with authentification. this is the regular check
> > stuff cyrus does on every startup. cyrus uses databases internaly to
> > store the header of the emails and the users information. These databases
> > are not present or the permissions on /var/lib/imap and the subfolders
> > have the wron permissions (must be writable and readable to the cyrus
> > user).
>
> But what did I do I only installed the RPM from the distro..
> I now changed the permissions to 770 for Imap..
> The other errors went away....
> Now more errors..
>
> Do I need to create users for IMAP now or what ??

Yes, carus-imap uses a different userbase than your host. That is the 
advantage of cyrus, you can have mail users that do not exist in the system. 
use cyradm for this stuff. Beware, a cyrus-imap user called hugo must created 
as user.hugo in cyradm (because it is a user, without the user. prefix it is 
a simple mailfolder). So please read the documentation of cyradm.

>
> All the users are normal unix box users...
>
> See this log below-----------------------
>
> Apr 11 12:28:57 lancer ctl_cyrusdb[27553]: done recovering cyrus databases
> Apr 11 12:28:57 lancer master[27552]: ready for work
> Apr 11 12:28:57 lancer master[27554]: about to exec
> /usr/lib/cyrus/bin/ctl_cyrusdb
> Apr 11 12:28:57 lancer master[27555]: about to exec
> /usr/lib/cyrus/bin/ctl_deliver
> Apr 11 12:28:57 lancer master[27556]: about to exec
> /usr/lib/cyrus/bin/tls_prune
> Apr 11 12:28:57 lancer ctl_cyrusdb[27554]: checkpointing cyrus databases
> Apr 11 12:28:57 lancer ctl_cyrusdb[27554]: DBERROR: error listing log
> files: DB_NOTFOUND: No matching key/data pair found

If you had not configured SSL/TLS this must fail. Should not be a problem. see 
the cyrus-imap configuration (usualy in /etc/master.conf).

> Apr 11 12:28:57 lancer ctl_cyrusdb[27554]: DBERROR: archive
> /var/lib/imap/db: cyrusdb error
> Apr 11 12:28:57 lancer ctl_cyrusdb[27554]: archiving database file:
> /var/lib/imap/mailboxes.db
> Apr 11 12:28:58 lancer ctl_cyrusdb[27554]: done checkpointing cyrus
> databases
> Apr 11 12:28:58 lancer master[27552]: process 27554 exited, status 0
> Apr 11 12:28:58 lancer ctl_deliver[27555]: DBERROR db4: 4 lockers
> Apr 11 12:28:58 lancer ctl_deliver[27555]: duplicate_prune: pruning back
> 3 days
> Apr 11 12:28:58 lancer ctl_deliver[27555]: duplicate_prune: purged 0 out
> of 0 entries
> Apr 11 12:28:58 lancer master[27552]: process 27555 exited, status 0
> Apr 11 12:28:59 lancer tls_prune[27556]: tls_prune: purged 0 out of 0
> entries
> Apr 11 12:28:59 lancer master[27552]: process 27556 exited, status 0

So there is a documentation what to do after the installation fo cyrus-imap. 
It is not realy complicated, but it does not work without these steps. I 
don't know the rpm installation so please read the docs (may be in 
/usr/share/doc/).

>                                                                21,1
>       Bot
>

Martin
-- 
------------------------------------------------------------
H E L I X Gesellschaft für Software & Engineering mbH
------------------------------------------------------------
Hanauer Landstrasse 52              Telefon (069) 4789 35-30
60314 Frankfurt am Main             Telefax (069) 4789 35-44
------------------------------------------------------------
http://www.helix-gmbh.net                info@helix-gmbh.net
------------------------------------------------------------

Attachment: pgpbEfjmXJczS.pgp
Description: signature