----- Original Message -----
From: "Rick Widmer" <[EMAIL PROTECTED]>
> Marcin Soltysiak wrote:
> > ----- Original Message -----
> > From: "Ken Jones" <[EMAIL PROTECTED]>
> >>Any votes on which way of specifying directories would be easier
> >>from the client program's point of view?
> >>a) full paths
> >>b) relative based on user or command
> > +1 for b) First, it would be a bit like chrooting, so potential
> > would have harder way to get out of ~vpopmail/. Second, would be easier
> > user if there was no need for repeting full path everytime.
> I disagree. If he chooses b, then you have to worry about what the
> rights of the current user is when composing commands. If he uses full
> paths, it doesn't matter what kind of user is at the browser, you always
> send the same command.
> For example, using b to create a VacationMessage file for [EMAIL PROTECTED]:
> Sys Admin would send:
> write_file /test.com/user/VacationMessage
> The Domain admin would send:
> write_file /user/VacationMessage
> And the user would send:
> write_file /VacationMessage
> It would be much easier to write code for using the daemon if everyone
> always referenced that file using the System Admin example, and you
> don't have to do the same job three different ways depending on who
> happens to be logged in.
> Remember, there will be a whole bunch of PHP code on top of the daemon.
Either I am missing something or... If we use full path then same operations
would look like:
Sys Admin would send same as
The Domain admin would send same as
And the user would send:
And this way we let the user know ~vpopmail. I know that in concepts,
ordinary user should not use plain vpopmaild protocol but PHP application,
but since we don't work in secret I can imagine that one day one of my
customers that feels geek in programing would come and request "Hey man,
where is your ~vpopmail? I don't like your admin UI and I want to write my
In case od b) I wouldn't have to tell him the path. He would just stick to
when logging as [EMAIL PROTECTED]