strange qmailadmin/vqadmin issues

[wency]

Hello, guys!
I have 2 linux boxes:

1st: RH9/vpopmail-5.4.0(with mysql)/qmailadmin-1.2.0/vqadmin-2.3.2

and

second: FC2/vpopmail-5.4.6(with mysql)/qmailadmin-1.2.1/vqadmin-2.3.6

I have tried to duplicate the first server into second - domains, users, passwords, etc. as described here:
http://www.qmailrocks.org/faq/?category=vpopmail#43
(all permissions/UIDs/GIDs are set correctly)

And all is working fine except the following:

1. qmailadmin running on the second box does NOT recognise my PREVIOUSLY created Mail Forwards/Aliases and Mail Robots.
However, when i create a new Mail Forward - there is no problems - it's working.
What i can see, is that when creating new Forward on the 2nd box - a record describing it appears into the vpopmail.valias table in mySQL.

But on the first box - i have about 20 fine-working mail-forwards and the vpopmail.valias table is empty.
When i create forward here with qmailadmin - a file named .qmail-forward_name is created in /home/vpopmail/domains/some_domain directory.

And the 2nd strange issue:
vqadmin running on the 2nd box RECOGNIZES all my old forwards, but DOES NOT recognize any newly created (with qmailadmin)

Where can be the reason? Only software versions differences may be?

[newkirk]

1.2.1 - released 10-Feb-04

Tom Collins
- Add note to INSTALL about requiring vpopmail 5.4.0 or later.
- Store aliases and autoresponders in valias table if vpopmail was
compiled with --enable-valias. Development of this feature was
sponsored by ACIS Pty Ltd <http://www.acis.com.au/>. [774819]
* If you are upgrading from a previous version of QmailAdmin and
used the --enable-valias option when building vpopmail, be sure
to download vpopmail 5.4.1 or later and use the dotqmail2valias
program to convert .qmail-alias files to valias table entries.

I was bitten by this as well, similar situation but with 5 nodes, hence a bigger mix of versions.

1.2.0 won't recognize the mysql valias table, while 1.2.1 will use only that since vpopmail was compiled with mysql support. (AFAIK there is no need to upgrade from 5.4.0 to fix this, simply to use the dotqmail2valias script that's include with later versions) You can either go all mysql and 1.2.1 or no mysql and 1.2.0, pretty much.

I don't think vqadmin works with mysql, only .qmail files. (I'm a few releases behind, though) We've been running for a while now reverted back to all dot-qmail for user-level control, until I have the chance to install several updates.

j