Odd. I can't explain it other than I must have done something in the
wrong order, because I installed qmailadmin-1.2.11 after recompiling
vpopmail-5.4.17 without mysql-limits, but I did a make clean and make
install-strip on qmailadmin-1.2.11 as you suggested and now it's reading
the .qmailadmi
Nick Bright wrote:
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 an
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 talkin
Greetings,
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 issue).
This issue started when I recompiled qmailadmin to remove
"domain-autofill", and I came across it once before long ago - but
lost/forgot the