Claudio Jeker wrote: > On Thu, Jun 06, 2002 at 02:08:20PM +0200, Torgeir Veimo wrote: > >>Claudio Jeker wrote: >> >>>On Thu, Jun 06, 2002 at 04:27:42AM +0200, Torgeir Veimo wrote: >>> >>>>From what I can see with qmail-ldap path 20020501a, if mailMessageStore >>>>is set, qmail-ldap now requires that directory to exist. Otherwise the >>>>mail for the recipient is deferred. >>>> >>>>This happens even if the entry has deliverymode set to forwardonly, and >>>>ldapdefaultdotmode is set to ldaponly. >>>> >>>>I didn't see this with qmail-ldap patch 20011001a (I think this was the >>>>last I used). Is this intentional? >>>> >>> >>>This is a qmail limitation. The MailMessageStore is used as homedirectory >>>for qmail-local. If it is not present and no homedir make script is >>>defined qmail-local will fail because the chdir to the homedir fails. >>> >>>Forwarding only users can be defined with only mail, >> >>mailForwardingaddress >> >>>and uid (with control/ldapuid and control/ldapgid used). >> >>But if deliverymode is set to local, then at least dirmaker is run. It >>is not run in this case, and I think this should be regarded as a bug. >>Either it shouldn't care about the missing directory, or it should run >>dirmaker. It shouldn't defer mail. >> > > No, this is not a bug. It's more a admin problem. > The -DAUTOMAILDIRMAKE option just enables the automatic creation of missing > Maildir structures on delivery and not the creation of homedirs. > For that use -DAUTOHOMEDIRMAKE option and a dirmaker script. > > If you create User without a homedir and do not enable AUTOHOMEDIRMAKE > qmail-ldap will always fail. > So eitehr you enable the auto homdir creation feature or you do not > specify a mailmessagestore (qmail uses the ~alias as home).
At least it creates some admin headaches. We have a system where users can toggle between forwarding or local storage. I would prefer just changing the deliverymode attribute. Like it is now, I have to remove the forwardingAddress when the user changes to local delivery (since the existance of mailForwarding address mandates forward in any case), and remove the mailMessageStore attribute when changing to forwarding. In java code this adds up to a lot of ModifyAttribute calls and error checking. -- -Torgeir
