5 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Maildrop delivery pro...
FromSent OnAttachments
Justin LambertMay 20, 2004 7:22 am 
Devin RubiaMay 20, 2004 10:15 am 
Justin LambertMay 20, 2004 11:04 am 
Devin RubiaMay 20, 2004 12:22 pm 
Justin LambertMay 20, 2004 2:06 pm 
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 delivery problems - signal 0x0BActions...
From:Justin Lambert (just@computility.com)
Date:May 20, 2004 2:06:45 pm
List:net.sourceforge.lists.courier-maildrop

Devin - thanks for your help. Setting the uidnumber_attr and gidnumber_attr in the maildropldap.config to dummy took care of the problem.

Justin

Well, according to this code snippet in maildrop/mdldap.c:

----------- values=ldap_get_values(ldap,entry,cfg->uidnumber_attr); if ( ldap_count_values(values) > 0 ) { rec->uidnumber = atoi(values[0]); ldap_value_free(values); } else { rec->uidnumber = cfg->default_uidnumber; }

-----------

all you have to do is not set a value for uid in LDAP and it will use the default.

If you need the uid attribute for Samba, then change the entry in maildropldap.config to an attirbute that doesn't exist in your LDAP entries. Eg.:

uid_attr maildrop_uid