Lloyd Zusman <[EMAIL PROTECTED]> writes: > [ ... ] > > But this brings up another question: how do I use webadmin to handle > *.example.com exactly the same as example.com in the "hosteddomains" > file? Specifically, how do I use webadmin to create "wildcard DNS" > entries in "hosteddomains" per the "Note" at the bottom of this > section in the documenation for "makehosteddomains"? > > [ ... ] > > Note: > > There is a period after the '@' character. If you want > all mail for ``any.thing.domain.com'' to be delivered as > though it were sent to ``domain.com'', you should > define an alias for the domain, for example: > > domain.com > .domain.com<TAB>domain.com > > In other words, how do I get an ".example.com<TAB>example.com" entry > into "hostededdomains" via webadmin?
It seems like I can't do this under webadmin. Also, there are a few other things that I still can't do with this utility. So this brings up a new question: I'd like my own, custom-written script to automatically get fired off every time I click on "Install new configuration" in webadmin. With such a script, I can make sure that extra entries such as ".example.com<TAB>example.com" get put into "hosteddomains" for every appropriate webadmin-based entry. Also, I could have this script automatically cause "userdb" entries to be created for certain entries in either "locals" or "hosteddomains" (I forget which at the moment). And I'm sure that there are other things that I would need it to do. Is there a way to plug in a custom, user-written program to get invoked whenever "Install new configuration" gets selected in webadmin, so that I won't to have remember to manually invoke this program every time I make webadmin-based changes? If such a thing isn't currently possible, I'm thinking of working on the following webadmin enhancement: In the COURIER/etc directory, the following two files could optionally exist: webadminpreinstall webadminpostinstall Each file would contain one line which consists of a the full pathname of an executable that gets invoked at the time that "Install new configuration" is selected. The program in "webadminpreinstall" would get invoked immediately after that link is selected, and before webadmin does anything; the program in "webadminpostinstall" would get invoked immediately after webadmin performs all of its installation tasks. Each script would be passed arguments that contain all of the important Courier directory pathnames, and any other configuration information that might be needed. If either or both of these files are missing, or if they don't contain a line that points to a valid executable, no pre- or post-installation processing would be performed. Also, these files would need to have very restrictive permissions (either 600 or 400), and the executables referred to would also need to have non-readable/writable/executable permissions for group and other. Yes, I know that this provides enough rope for us to hang ourselves good. However, this will be optional, and therefore, those of us who make use of this feature would be willing to take responsiblity for the consequences. Given that the guts of webadmin are written in perl, it should be fairly easy for me to come up with a small patch that implements this functionality. What do you folks think? -- Lloyd Zusman [EMAIL PROTECTED] God bless you. ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
