|
>> Is there an easy way to enable logging with tmda-cgi for
installs and
>> uninstalls? > >No, not currently. I've held off on all logging-related stuff until >TMDA embraces the new Python logging module. That way I won't have to >rewrite it later. > >> Basically being able to keep track of which users have tmda installed. >> A simple log file with current users installed or even a simple log file >> like so. >> [EMAIL PROTECTED] - installed >> [EMAIL PROTECTED] - Installed >> [EMAIL PROTECTED] - installed >> [EMAIL PROTECTED] - uninstalled >Instead, can I suggest just using 'nix utilities to do this search? >For example, if you are using vpopmail and qmail, you can do the >following: > ># grep -l tmda `find /home/vpopmail/domains/ -name ".qmail-*"` \ > |grep -v \\-default > >Sneaky, huh? > >Gre7g. Okay.
Since my upgrade to vpopmail 5.3.20 I no longer
need to put anything in the parent directory.
By enabling the address extension support during
compile of vpopmail dynamic addresses are easily followed.
This has made my life a ton easier because there
are not 10,000 .qmail files in the parent directory (plus I am not certain how
qmail would like that anyway).
So all I have to have is a single .qmail file in
the users directory.
This actually solves all the problems I mentioned
before (like users with a dot in there username and many others I brought up
before) because all that is not needed with the new vpopmail.
The one problem it brings up is that I no longer
know who has it installed easily.
I can do a search of some kind but it will take a
long time because you have to look several levels down in some cases (like
/var/qmail/vpopmail/domains/me.com/0/s/4 ).
It is not a problem; thanks for the suggestion and
I will wait until tmda-cgi embraces the logging module.
Sam
|
