Currently ( I think ) qmailadmin does not support vpopmail's valias/database code. It just uses the .qmail-username files.
If anyone has code to support valias in qmailadmin, please post a link to the patch. Ken Jones On Tuesday 07 January 2003 09:40 am, Benno wrote: > Hello, > I installed a system with qmail+mysql the following packages: > qmail-1.03 > qmailadmin-1.0.6 > vpopmail-mysql-5.2.1 > > it works ok, mailboxes are stored in the mysql database but > the behaviour of qmailadmin in conjunction with aliases/forwards > is not ok. > > Basically you can either create a mailbox with the vadduser command or > with qmailadmin > and in both cases the user gets stored in the mysql database. (table > vpopmail) > This is ok. > > But when you add new aliases/forwards, the valias command does the correct > job and adds the enty in the mysql database (valias table) but when I > add and alias/forward > with qmailadmin, it creates a file in the > vpopmail/domains/mydomain.com/.qmail-myaliasname > > Of course aliases/forwards created with the valias command are not > visible in qmailadmin > when accessing aliases which is very annoying since I�d like to import a > list of forwards from > a textfile using the valias command and later edit them in qmailadmin. > > My question: is the behaviour of qmailadmin correct (storing mailboxes > in mysql and forwards/aliases in a file) or do you need to perform some > special steps during compilation ? > > thanks in advance for infos > cheers, > Benno
