<[EMAIL PROTECTED]> wrote:For user [EMAIL PROTECTED], you'll need files .qmail-joshua/.qmail-joshua-default in josh's directory. These should route email to TMDA, with a command-line parameter to specify the location of joshua's TMDA configuration. Similarly, you could have .qmail-xxx/.qmail-xxx-default for [EMAIL PROTECTED] etc.
I see! So the only caveat is that joshua can't modify his TMDA config; it has to be in josh's directory, although there can be more than one in josh's directory. This will work for me.
(CC'ing list again in case it's useful to other people)
tmda-rfilter can take a -c option, which specifies a file to use instead of ~/.config. This file can specify paths for all other things, such as filters, lists, etc.
Thus, the .qmail files in josh's directory couldn't be modified by joshua, but TMDA could easily be told to get the configuration data from some other directory that joshua could modify.
Note that you would have to be a little careful of file permissions - maybe make a new group that both josh and joshua are in, and have all TMDA files (config, whitelists, filters, logs, ...) and directories owned and read/write by both josh and joshua - both joshua and the TMDA process running as josh will need to read/write these files. Umask may help with this for joshua... (Depending on how you configure TMDA - it may need to write to log files and update whitelists. It will certainly need to update the pending directory)
-- Stephen Warren, Software Engineer, NVIDIA, Fort Collins, CO [EMAIL PROTECTED] http://www.wwwdotorg.org/pgp.html
signature.asc
Description: OpenPGP digital signature
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
