On Thursday 27 March 2003 14:35, you wrote:
Could someone provide details of what vlimits patch does.
I have seen some interesting threads about it
thanks
Matt.
basically it lets you limit the usage of a vpopmail controlled domain.
this means:
limit the max no of pop
On Tuesday 25 March 2003 18:25, Brian Kolaci wrote:
Do you think we need both domain permissions and
default new user permissions for each type of permission?
(This is the case for quotas, a domain limit and a default
for new users).
I like the idea of having both (which just generates more
On Tuesday 25 March 2003 18:25, Brian Kolaci wrote:
Do you think we need both domain permissions and
default new user permissions for each type of permission?
(This is the case for quotas, a domain limit and a default
for new users).
I like the idea of having both
this enforces the disable_* vlimits:
e.g: if vlimits.disable_imap=1 it is the same as if every user has the NO_IMAP
gid flag set.
i'm going to post (a very similar one) tomorrow for .qmail-limits files.
is there vlimit support being added for postgres/sybase/oracle ?
---
This is very good, however you may want to move this
out of vmysql.c and put it directly in vpopmail.c
for the add_user routine.
vlimits isn't only for mysql. It also uses the
.qmailadmin-limits file for non-mysql implementations.
So the structure function vget_limits() is valid
with or
On Tuesday 25 March 2003 17:34, Brian Kolaci wrote:
i'm going to post (a very similar one) tomorrow for .qmail-limits files.
:)
i think this should stay in the vauth_getpw function (which is in vauth.c).
this way, when you later decide to disable_imap=1 you won't have to change it
for all the
Ahh, I think we had different thoughts on that.
When I originally sent out the request for comments
for the vlimits, I thought the disable_ routines
were to be the defaults for new users. This was the
original intent from the responses I got. This way you
would be able to shut off certain
