Alejandro Aguilar Sierra wrote:
It seems to me the way to handle that is to have the plugin call
vpopmail functions directly. I see QmailAdmin as an adapter between the
CGI interface to a web server and the vpopmail functions. How would
another applicaion use it?
Qmailadmin runs as the vpop
> It seems to me the way to handle that is to have the plugin call
> vpopmail functions directly. I see QmailAdmin as an adapter between the
> CGI interface to a web server and the vpopmail functions. How would
> another applicaion use it?
Qmailadmin runs as the vpopmail user and have all the pr
Alejandro Aguilar Sierra wrote:
A way to let final users to do some basic tasks (like change passwords,
forwards, filters) from another application like a squirrelmail plugin
would be fine.
It seems to me the way to handle that is to have the plugin call
vpopmail functions directly. I see Qmai
On Mon, 2 Feb 2004, Rick Widmer wrote:
> All suggestions and help are welcome!
A way to let final users to do some basic tasks (like change passwords,
forwards, filters) from another application like a squirrelmail plugin
would be fine.
--
Alejandro Aguilar Sierra
[EMAIL PROTECTED]
Sorry, this should have gone to the list the first time...
Ken Jones wrote:
Hi Rick,
Use the ones without the "_" characters. The ones with the "_"
are the lower level functions which encapsulate the details of
each authentication backend.
OK.
What kind of changes are you planning on putting i
On Feb 2, 2004, at 7:47 PM, Rick Widmer wrote:
In trying to understand vpopmail so I can work on QmailAdmin, I've run
into some things I don't understand. Could someone comment on why the
following functions are almost identical? Which should I use?
vadddomain vauth_adddomain
vdeldomain
In trying to understand vpopmail so I can work on QmailAdmin, I've run
into some things I don't understand. Could someone comment on why the
following functions are almost identical? Which should I use?
vadddomain vauth_adddomain
vdeldomain vauth_deleomain
vadduser vauth_ad
