On 17 Aug 2001 13:28:11 -0500, Bill Shupp wrote:
> on 8/17/01 1:09 PM, Gabriel Ambuehl at [EMAIL PROTECTED] spake:
>
> > I know this will be considered blasphemy or something cause it would
> > probably involve a rather serious amount of work, but wouldn't it be
> > wiser to stick all this stuff, including things like fetching all
> > users of a domain etc pp into libvpopmail so other code could use it
> > without having to dig for it in qmailadmin?
> >
> > Best regards,
> > Gabriel
>
> Listing all users IS in the library via "vauth_getall". However, showing
> aliases/forwards isn't yet (only mysql, I think). Ken mentioned to me that
> he hopes to integrate the valias functions into the API, but has not had
> time to do it yet.
>
> I tend to think that while .qmail files are still used for alias/forwards
> for some auth modules, it would be easier to manage them when kept in the
> domain directory, rather than user directories.
I just looked through the vpopmail code. Take a look at the
vpalias.c file. This file is included if --enable-valias=n.
It has all the functions needed to manage .qmail files
in a domain directory. For example:
char *valias_select( char *alias, char *domain );
char *valias_select_next();
int valias_insert( char *alias, char *domain, char *alias_line);
int valias_delete( char *alias, char *domain);
char *valias_select_all( char *alias, char *domain );
char *valias_select_all_next(char *alias);
With these functions you can manage all the .qmail files.
the valias command line program uses these functions.
qmailadmin hasn't been updated to use these functions.
btw: for vpopmail-4.10, it looks stable. Unless there are
any more bugs or major features needed, lets move it
to a stable 5.0 release.
Ken Jones
