Claudio Jeker wrote: > On Thu, Jun 06, 2002 at 04:58:02PM +0200, Torgeir Veimo wrote: > >>Claudio Jeker wrote: >> >>>On Thu, Jun 06, 2002 at 04:16:16PM +0200, Torgeir Veimo wrote: >>> >>> >>>>Claudio Jeker wrote: >>>> >>>> >>>>>On Thu, Jun 06, 2002 at 02:08:20PM +0200, Torgeir Veimo wrote: >>>>> >>>>>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. >>>> >>> >>> >>>No. In your case just compile a qmail-ldap vewrsion with autohomedirmake >>>option enabled and a dirmaker script. Then if a homedir does not exist the >>>homedir will be created (even if forwardonly is set). >>>You need only to set/unset mailForwardingAddress to toggle the behaviour.
After checking and cheking, this is actually the case. (Not a big surprice really.) I walk into the corner in shame over not testing this properly before whining on the list. -- -Torgeir
