Tim, Has this been further discussed yet on workers? I checked the archives, and I didn't see anything but this one message. I didn't miss any, did I?
How would you recommend that we proceed with this? Should I draft an explanation/information message and post it to the workers list to brief the people on the workers list? Kinda like a inter-list RFC? :) I'd really like to get their feedback on the #3 option before I start coding. Thanks, Jesse On Sunday 15 December 2002 22:09, Tim Legant wrote: > "Jesse Guardiani" <[EMAIL PROTECTED]> writes: > > ----- Original Message ----- > > From: "Michael Schler" <[EMAIL PROTECTED]> > > Sent: Sunday, December 15, 2002 3:40 PM > > > > > 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. > > That's correct. I think it's a compile-time option for vpopmail, but > I could be wrong about the later versions. > > > > I 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. > > I concur, as well. > > [...snip 3 options, of which I prefer number 3...] > > > 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.) > > I'm sending this to -workers to move the discussion over there, but > I've CCed this last message to -users as well. > > I think a simpler way to do this might be to maintain a separate > directory structure for TMDA configs and filters and not put all that > stuff into the users' maildirs. On the other hand, since the .tmda/ > directory has a leading '.', it should be safe. > > Anyhow, it would mean that we always know where things are, so none of > the three options above would be necessary. It also means that the > admin has a bit more work to do each time s/he creates a new virtual > domain and new users. > > A final possibility would be to code the algorithm that vpopmail uses > to create large directory structures into Python. This has the same > problem of parsing 'vuserinfo' output, though, in that it's possible > it might change and TMDA would break. > > VMailMgr comes with a nice little Python library that can give you all > this information, but a quick Google search didn't find a Python > module/wrapper for vpopmail. > > The more I think about it, I lean toward option three, the external > program that returns the user's home directory. I think it's the > cleanest of the options and the most flexible. > > > Tim > _____________________________________________ > tmda-users mailing list ([EMAIL PROTECTED]) > http://tmda.net/lists/listinfo/tmda-users -- 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. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
