Brian Kolaci wrote: > > Brain, I'm on the list. There's no need to send me a copy and > the list. > Just reply to the list please. I get enough mail as > is, I don't need two > copies of the same message :) > > When you hit "reply", it sends it to you, not the list. > I just added the list as a CC before.
That's because this list is set for reply to poster. > > <snip> > > At any rate, the support added to auto-create was > added as a fail-safe recovery method, should the directory Did you actually read the change log entry?? How do you get "fail-safe recovery method" from "vdelivermail will auto create a users directory if thier directory value in thier authentication structure is blank. This can be used by sql based systems, or ldap systems. Users can be created and inserted into the database, and if their path value is left blank, vpopmail will use the bigdir directory layout algorythm to create a directory and update the authentication database. So, users can be created by just adding them to the database and leaving thier directory path blank." The key part, in case you missed it, is "Users can be created and inserted into the database, and if their path value is left blank, vpopmail will use the bigdir directory layout algorythm to create a directory and update the authentication database. So, users can be created by just adding them to the database and leaving thier directory path blank." That sure doesn't look like a "fail-safe recovery method" to me. That looks like inserting directly into the database for user creation was specifically designed in. > get corrupted or deleted by mistake. It appears you're > exploiting a recovery mechanism. This may be fine for Nope, read above. > your implementation, however its most likely to come > back and haunt you in the future. Don't think so. See above. > > Going behind the scenes to insert directly into the > database is a kludge. For many users, the database > isn't an option. The repository can be many backing > stores, one of which may be MySQL. > And the authors spefically put in support to do exactly that. Again, see above. > If you don't like the supplied methods to create user > accounts, you're welcome to add your own. However keep But I am using a supplied method. See above. > in mind that other things go on in the API like validation > and such, and it allows a central place to implement > any other "side effects" that may be required at account > creation time. This would most likely be the place to > enforce the vlimits recently added to the vpopmail library. > > Bypassing the intended API is a kludge. I agree with you there. I just don't see that I'm bypassing the intended API. I'm using a method documented and suggested by the authors. > > Brian Dave
