On Sat, Aug 02, 2003 at 02:48:40PM -0600, Roberto Carlos Navas wrote: > Will this patch still behave under this conditions: > When the ldap entry looks like this: > > dn: [EMAIL PROTECTED], ou=People, o=Telemovil > mail: [EMAIL PROTECTED] > objectClass: top > objectClass: qmailUser > mailMessageStore: /mailstore/telemovil.com/883/8832010 > uid: 8832010 > mailHost: mail.telemovil.com > cn: Roberto Carlos Navas > mailAlternateAddress: [EMAIL PROTECTED] > mailQuota: 500000000S,5000C > deliveryProgramPath: /lmtools/bin/notify.pl > mailReplyText: Prueba de Mensaje de Vacaciones... > deliveryMode: forwardonly > mailForwardingAddress: [EMAIL PROTECTED] > > The result is this: > > delivery 20067: deferral: > Uh-oh:_deliveryMode_has_prog_delivery_but_has_forwardonly_set._(#4.7.0)/ > > I'm using 20021201a and all versions after that do the above... >
This was a bug that was fixed somewhen in 2003. deliverymode forwardonly is very restrictive, similar to setting the x-bit on a .qmail file. forwardonly is intended for forwarding only account, anything else will cause this error. My tip, remove the forwardonly deliveryMode from you ldap db (sed/awk is you friend). > Also one question: I'm serving 2 domains with qmail-ldap: mydomain.com and > mydomain.net, what is the best way to make qmail-ldap to execute a delivery > program with each incoming local message and still do a normal maildir > delivery for all mydomain.com accounts?... Also, I need that program to be > executed no matter what deliveryMode the user has. > That's a tricky question. If the users have access to all entries in their ldap entry it is not possible to solve your problem. As soon as you can restrict some values (e.g. deliveryMode) you can build such a system. I would restrict deliveryMode to localdelivery und set the aliasempty (last arg to qmail-start) to something like: "|program to execute \ ./Maildir/" -- :wq Claudio
