7 messages in net.sourceforge.lists.courier-maildropRE: [maildropl] Maildrop at Debian Sarge
FromSent OnAttachments
Sérgio FerreiraNov 7, 2005 10:30 am.dat
Tony EarnshawNov 7, 2005 12:54 pm 
Dave AugustusNov 7, 2005 1:21 pm 
Sérgio FerreiraNov 8, 2005 4:35 am 
Sérgio FerreiraNov 8, 2005 4:43 am 
Tony EarnshawNov 9, 2005 2:11 am 
Sérgio FerreiraNov 9, 2005 8:03 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [maildropl] Maildrop at Debian SargeActions...
From:Sérgio Ferreira (serg@minc.gov.br)
Date:Nov 9, 2005 8:03:39 am
List:net.sourceforge.lists.courier-maildrop

Hi Toni,

-----Original Message----- From: cour@lists.sourceforge.net [mailto:cour@lists.sourceforge.net] On Behalf Of Tony Earnshaw Sent: Tuesday, November 08, 2005 1:09 PM To: cour@lists.sourceforge.net Subject: RE: [maildropl] Maildrop at Debian Sarge

ty den 08.11.2005 Klokka 10:07 (-0200) skreiv Sérgio Ferreira:

[...]

maildrop 1.7.0 Copyright 1998-2003 Double Precision, Inc. GDBM extensions enabled. Maildir quota extension enabled. Virtual user database extension enabled. Virtual user database via LDAP extension enabled. This program is distributed under the terms of the GNU General Public License. See COPYING for additional information.

Newer maildrop versions split up authentication and maildrop itself. You get a little more functionality, plus more modularity and better integration with Courier IMAP.

Earlier I tried to install only courier-maildrop 2.0.1, but seems not work in a different way. Should I install all courier packages (base, imap,ldap, and so)?

[...]

grep '^[^#]' authldaprc?

Hmmm ... your maildropldap.config looks like a recent Courier Authlib authldaprc, which is like an older Courier IMAP authldaprc.

I compared It trough the docs I found before, and thought the same as you. As I am not an expertise to make question about I just followed the outdated docs.

Here's a maildrop 1.7.0 LDAP config that works:

hostname mercurius.intern uidnumber 18 # vmail gidnumber 18 # vmail mail_attr mail # user's mail address uid_attr uid uidnumber_attr dummy gidnumber_attr dummy maildir_attr mailmessagestore #full path to user's Maildir homedirectory_attr mailmessagestore quota_attr quota basedn dc=voorbeeld,dc=nl filter &(&(objectclass=qmailuser)(accountstatus=active)) binddn cn=proxy,dc=voorbeeld,dc=nl bindpw proxypassword timeout 10 search_method uid

I tried It, but maildrop seems to be ignoring the maildropldap.config file. I copied this file to /etc/ and /etc/courier/, this way remains no doubt about the path. Things are little strange, Maildrop is querying straight to LDAP directory. I am guessing he is not using authldap config file too, because homeDirectory of authldap file is pointing to mailMessageStore and Maildrop is retrieving a real value of homeDirectory of user that resides on LDAP.

If am right, how that is possible??? and where is the config file that keeps this configuration of maildrop???

Maildrop is not using his owner user to get access on mail home directory.This is why "unable to change to home..." message is raising.

The maildroprc isn't worth commenting on, since it isn't finished.

I not set my focus on It, shouldn´t be a problem not use It at this momment? Or should I provide a good one right now????

Best,

--Tonni

Thanks for your attention,

Sergio