See comments below... Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net
We are actively looking for companies that do a lot of long distance faxing and want to cut their long distance bill by up to 50%. Contact [EMAIL PROTECTED] for more info. ----- Original Message ----- From: "Michael Schler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, December 15, 2002 3:40 PM Subject: Re: tmda-ofmipd + vpopmail IP-based domains > Or would it be better to create a more flexible switch/config-file-variable > that > allows the admin to set the 'DATADIR' variable via a command line string, > such as: > > --set-DATADIR=/usr/local/vpopmail/domains/$DOMAIN/$USERNAME/.tmda >This won't work for many domains and/or users as vpopmail is starting at some point to create further subdirectories. I.e. the path can >be > /usr/local/vpopmail/domains/0/$DOMAIN/b/$USERNAME/.tmda >as well. In don't think there is another reliable way besides > /usr/local/vpopmail/bin/vuserinfo -d <email_address> >to get the correct directory for a specific email-address/user. I think you're correct in that. Someone could write a quick C program to retrieve the data directly, but otherwise it would mean parsing the 'vuserinfo' output. I see three options: 1.) If we parse the 'vuserinfo' output, then everything stays python, which is good, but changes to vpopmail down the road may lead to 'vuserinfo' being displayed differently (in fact, you can probably count on it!), and this would mean more maintenance work on a version to version basis, as well as 'lag' when a new version of vpopmail comes out that has an incompatible 'vuserinfo' output. 2.) If we write a simple C function, then something has to actually be compiled for vpopmail support. This means that a configure script will have to be generated and maintained. But, on the plus side, once it's done, it'll work until the vpopmail API changes, which isn't likely anytime soon. And it doesn't have to be compiled unless someone needs vpopmail support. 3.) Maybe we should just create a tmda-ofmipd command line flag that says "--virtual-domain-interface-program=my_interface_program". Then, when it comes time to find the user's home directory, tmda-ofmipd checks to see if "--virtual-domain-interface-program" has been specified, and if it has, calls the given program. tmda-ofmipd would populate the "$tmda-ofmipd-domain" environment variable and the "$tmda-ofmipd-user" environment variable of the "my_interface_program". The "my_shell_script" could be a shell script (VMailMgr), or a C program, or any other kind of program. The important thing is that it makes use of the "$tmda-ofmipd-user" and "$tmda-ofmipd-domain" environment variables, and properly returns the user's home directory. The nice thing about this setup would be modularity. If some other virtual domain manager comes along in the future, "Joe Sysadmin" can write his own Perl script to retrieve the necessary info without bothering the tmda-ofmipd developers. Tim? What do you think? (And BTW, I AM going to join the Workers list and discuss this there, but this is my weekend off, so I thought I'd wait till monday to set up my Maildrop filters.) >Michael >_____________________________________________ >tmda-users mailing list ([EMAIL PROTECTED]) >http://tmda.net/lists/listinfo/tmda-users _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
