Update to this issue:
It seems a little odd, but with vpopmail compiled for
"--disable-mysql-limits" if the "limits" table exists, vmoddomlimits
will apply settings to that table. If the table is deleted, it applies
them to the .qmailadmin-limits file.
So now, vpopmail and vqadmin are talking to .qmailadmin-limits; all that
remains is to get qmailadmin to talk to .qmailadmin-limits.
- Nick Bright
Tel 888-332-1616 x 315
Nick Bright wrote:
I've got an installation of vpopmail 5.4.17, vqadmin 2.3.6, and
qmailadmin 1.2.11 (updated vqadmin and qmailadmin trying to fix this
This issue started when I recompiled qmailadmin to remove
"domain-autofill", and I came across it once before long ago - but
lost/forgot the fix.
What happens is that vpopmail (even when compiled with
--disable-mysql-limits) stores all information in the SQL table "limits".
Qmailadmin, regardless of how vpopmail is compiled, will only look in
the SQL table for limit information, and does not have a compile flag to
tell it to pay attention to the .qmailadmin-limits file.
Vqadmin, regardless of how vpopmail is compiled, will only look at the
.qmailadmin-limits file, and does not have a compile flag to tell it to
look in the database instead.
Though I would prefer that things look at the .qmailadmin-limits file
(since that's where all the limits are defined currently) I don't really
care if the limits are in .qmailadmin-limits, or in the sql table, I
just need to know how to get _all_ of the applications to look at the
same thing. If it has to be in SQL, I can go through all my domains and
put them in the database.
Any advice is welcome, thanks in advance.