Philip Hazel wrote: > Consider the case when the transport ends up with > > directory = some string expansion > > where the expansion sometimes yields /some/maildir (for a non-folder > delivery) and sometimes yields /some/maildir/.subfolder - depending > on the local part or local part affix, or on $address_data, for > example. > > Then the new boolean option will have to do exactly the same > expansion plus a messy test in order to decide whether to yield true > or false.
Well, I'd leave that to the user. :o) Consider my simple example, extended by "subfolder_delivery": directory = ${lookup mysql{SELECT maildir ...}}\ ${if def:h_X-Spam:{/.Junk}{}} subfolder_delivery: ${if def:h_X-Spam:{yes}{no}} Documentation should be explicit about that, though. > Exim already recognizes existing maildirfolder files for quota > calculations. (And there is also the quota_directory option.) The > issue is just about whether to create them. Hmm, so quota calculation is just done *after* delivering to ~/tmp, I guess? > Hmm. I suppose one approach would be (subject to a simple boolean > yes/no) to automatically create maildirfolder if the last component > of the delivery directory starts with a dot. Would that work, do you > think? I don't think so, as any directory may start with a dot. A maybe not too farfetched example would be maildirs of the form "/home/of/user/.Mail". lg, daniel -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/