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:Devin Rubia (dev@thezone.net)
Date:May 20, 2004 12:22:44 pm
List:net.sourceforge.lists.courier-maildrop

On Thu, May 20, 2004 at 12:59:42PM -0500, Justin Lambert wrote:

Ahhh that makes sense. I was thinking that the --enable-maildrop-uid=vmail and --enable-maildrop-gid=vmail would take care of that and only run as vmail. These users are samba users as well as virtual mail users so I'd like to find a way around adding an ldap attribute just for the setuid stuff.

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

-- Devin