Rick Romero wrote: > On Tue, 2003-03-25 at 09:44, Dave Weiner wrote: >> Rick Romero wrote: > >> No it's not. The ChangeLog for 4.9.3 specifically mentions inserting >> directly into the database as a valid method, as specific support >> was added >> for just that. > > You RTFM'd? Damn you! :P
Yes I did :) > >> But the original poster *is* using the tools given to him. The >> problem is >> qmailadmin isn't using the API >> >>> >>> The first kludge isn't working 100%, hence the original post. :) >>> >> >> Sorry, I don't think it's a kludge. And it is working. What's not >> working >> is qmailadmin. > > I still disagree, because it seems like the call to create the mail > directory by vdelivermail is just a fallback method. Since Nope, it's intended to do exacly what it's doing -- create the user directory if it's blank in the authentication backend. > QmailAdmin doesn't deliver mail, the 'backup' doesn't get called. No, but it should follow the same methods that vpopmail does. If the directory field is blank in the authentication backend, when that user is accessed via qmailadmin, it should auto create the directory. > We're just not going to see eye to eye on this one :P > > QmailAdmin probably shouldn't give that error though. > > I don't have a good solution for that error. Creating the mail > directory feels like there's not enough control.. but then the user > could send themselves an email to create it anyways.. The user entry still has to be made in the authentication backend before the auto creation of the directory happens. If your end users can do that, then you've got bigger problems to worry about :) > > I don't know. Maybe that's why vadduser creates the maildirs instead > of leaving > it to vdelivermail? > > Rick Dave
