On Thu, 2003-11-20 at 12:51, Mitch (WebCob) wrote: > Hmmm - silence eh? > > What about some way I could set environment variables before calling > maildrop and then import them from there? > > Would it be possible (instead of using default delivery to maildrop) to do > default delivery to another program, which could set up the environment for > maildrop with all the extra varables needed for filtering, and then call > maildrop? > > How would that work? > > I can write that script, just need to know if I'm on the right track? > > Instead of: > DEFAULTDELIVERY="| exec /usr/lib/courier/bin/maildrop"
Why you use 'exec' here? Some performance gain? > > I could call: > DEFAULTDELIVERY="| exec /mydeliveryprogram" > > Which does it's database queries, sets up environment variables, and calls > maildrop. Maildrop can then import the know environment variables needed, > run, and exit. > > my program would then exit with the return code given by maildrop. Why not set the enviroment variables in your program and then 'exec' maildrop? In this way your program don't need to be aware of the return code. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
