"Jason R. Mastaler" <[EMAIL PROTECTED]> writes:
> Timothy Legant <[EMAIL PROTECTED]> writes:
>
> > Modified Files:
> > ChangeLog tmda-rfilter
> > Log Message:
> > Call new function setvuserhomedir during argument processing if the -S
> > (--vhome-script) flag is given to update $HOME with the virtual user's
> > home directory.
>
> Cool. Should tmda-vdomains.html be updated accordingly?
Yes. That's next on my list, as soon as I get my db proposal
finished. It's about halfway done. I expect to post that today.
> > + parts = os.environ['EXT'].split('-confirm-', 1)[0].split('-')
>
> You should probably use Defaults.TAGS_CONFIRM[0] instead of 'confirm'.
I can't use anything in Defaults. That's probably the biggest problem
I had thinking through all this stuff. Defaults reads the config
files, but for '~' to work properly in config files, it has to be set
before the config files are read. Chicken and egg problem.
That's going to be one of the design changes I push for post 1.0. I'd
like to see system-wide configuration options like
MAIL_TRANSFER_AGENT, RECIPIENT_DELIMITER, etc. loaded very early so
code like this can use them. Maybe the distinction isn't "system-wide
options" so much as "non-path options". It remains to be seen.
Perhaps the message could even be read from stdin and variables like
TMDA_RECIPIENT set up *before* the user-level configuration is loaded.
I'm not sure exactly where to draw the line to determine what gets
loaded first and what gets loaded later, but it's become clear while
trying to make this virtual domain stuff work that we should seriously
consider breaking the config into two steps with the opportunity for
TMDA code to run in-between.
Tim
_________________________________________________
tmda-workers mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-workers
