> > Not anymore. This has changed with 5.3. The .qmailadmin-limits
> > is now extended into vpopmail and is now enforced at the domain
> > level as well as setting default quotas for users. The old
> > method allowed you to set a single site-wide HARD_QUOTA.
>
> And how does that a
> Brian Kolaci wrote:
>
> > Yes, however when that was done, there was never a
> > concept of enforcing limits back then. Justin just submitted
>
> Again, I think you're wrong. As early as 4.1 there was quotas of some sort.
> I believe the limi
> Did you actually read the change log entry?? How do you get "fail-safe
> recovery method" from "vdelivermail will auto create a users directory if
> thier directory value in thier authentication structure is blank. This can
> be used by sql based systems, or ldap systems.
> Users can
> Brain, I'm on the list. There's no need to send me a copy and the list.
> Just reply to the list please. I get enough mail as is, I don't need two
> copies of the same message :)
When you hit "reply", it sends it to you, not the list.
I just added the list as a CC before.
At any ra
> Rick Romero wrote:
> > IMHO, manually inserting records into MySQL is a bit of a kludge. It
> > would probably be better to create a flat file of users / passwords,
> > and let perl loop through that and pass the data to vadduser.
>
> Ok Rick, let me get this straight -- you think
Yes, you need 5.3.19 or up.
Brian
> On Mon, 24 Mar 2003 14:31:53 -0600
> Ken Jones <[EMAIL PROTECTED]> wrote:
>
>
> > In the vpopmail source code, copy the vlimits.h file
> > to the ~vpopmail/include directory.
>
>
> I looked in the source of vopmail 5.2.1 but I can't find
Sorry, my mistake. I was baffled for a bit since it was
working in my copy. I compared it to the 1.0.14 out there
and found the diffs. I originally made a patch for 1.0.12.
When re-creating the patch for 1.0.13 I apparently left something out.
Please apply this patch to 1.0.14 and it should be
char *get_quota_used(char *dir) {
char *tmpstr;
char tmpbuff[MAX_BUFF];
***
*** 265,270
--- 266,272
tmpstr = tmpbuff;
return tmpstr;
}
+ */
int quota_to_bytes(char returnval[], char *quota) {
char *tmpstr;
double tmp;
**
quota usage to maildir quota
usage. I've also written the vlimits() API's incorporated
into vpopmail.
Thanks,
Brian
> On Monday, March 17, 2003, at 01:22 PM, Brian Kolaci wrote to the
> qmailadmin list:
> > vmoduser needs to be updated to write a properly format
ata to the field. Currently, it just writes the information
verbatim from the command line.
Thanks,
Brian
> On Monday, March 17, 2003, at 05:56 AM, Brian Kolaci wrote:
> > The abbreviations for Megabytes & Kilobytes "M", "m", "K" and "k"
so that
> others aren't confused, scared, etc.
>
> Matt
>
> On Monday, March 17, 2003, at 07:56 AM, Brian Kolaci wrote:
>
> > The abbreviations for Megabytes & Kilobytes "M", "m", "K" and "k"
> > have al
The abbreviations for Megabytes & Kilobytes "M", "m", "K" and "k"
have all been deprecated in the latest release of vpopmail
and qmailadmin. You should use all numbers now. The limits API
doesn't support this (and probably won't due to the database
holding numbers and not strings for these value
Yes, this was discovered over a month ago (I posted a patch
way back when), but it appears that it didn't get included.
I'm actually working on updating qmailadmin & vqadmin to
use the vlimits API and the maildir++ quotas functions.
I'll send a patch as soon as its ready.
Thanks,
Brian
> I f
> > > Anyway, the point of this is: I'd love to see this thing in the next
> > > production release. Is anyone planning a new production release soon? Or
> > > is it still up in the air?
> >
> > Kinda of along these lines, I've implemented the use of a FORM to
> > automatically log use
Yes, the value should be an integer only.
The new maildir quota actually wants either
just a number or a number followed by "S".
The new format wants 5000 (or if you really
want 50 Meg, use 52428800).
The ".00" will hose it up. I recall sending
in a patch for this, but it appears it wasn't
a
Quotas were talked about *alot*, before and after the limits
API patches I submitted. I've had the domain quota using system
quotas over a year. What was asked for was a solution to implement
domain quotas (not pooled allocation scheme), which I've had running
for a bit over a month (which take
> >Just make sure this new enhancement does not disturb
> >the current domain quotas as specified in the qmailadmin-limits
> >API. Make sure you add a new attribute rather than change the usage
> >of the current implementation. I actually use these to implement real
> >quotas on my sys
Just make sure this new enhancement does not disturb
the current domain quotas as specified in the qmailadmin-limits
API. Make sure you add a new attribute rather than change the usage
of the current implementation. I actually use these to implement real
quotas on my system. We ensure that all
qa_sort() is the comparison function that's fed into qsort.
In any case, qsort is always called.
Brian
> At 10:45 24/01/2003 -0500, Brian Kolaci wrote:
>
> >Did you leave the function qa_sort() there or remove it?
> >It should have stayed exactly as it was before
t; >- free(namelist[m]);
> > }
> >-
> > closedir(mydir);
> > free(namelist);
> >
> > if (AdminType == DOMAIN_ADMIN) {
> >--- 176,186
> > fclose(fs);
> > k++;
> > }
>
else { return 1; }
! sprintf(returnval, "%-2.2lf", tmp);
return 0;
}
int quota_to_megabytes(char returnval[], char *quota) {
char *tmpstr;
! double tmp;
if (quota == NULL) { return 1; }
! if (tmp = atol(quota)) {
! if (tmp != 0)
Hi Justin,
I believe I already removed the fts_* functions in that release
that you had and submitted the patch. That was a long time ago...
Thanks,
Brian
> Sorry, I should have been watching the list a little closer. I may have
> been responsible for the fts_* functions that are in util
evel of
API's will exist in all the licensed O/S's among other things.
Thanks,
Brian
> At 04:33 AM 01-17-2003, Brian Kolaci wrote:
>
> >Me too,
> >
> >I tried replying last night, however the "efilter"
> >blocked my response.
I'm not sure where you got that, however it looks
more like it was "left behind". POSIX.1 was complete
back in 1990. fts was not included. In fact, its not
even on linux. So yes, its certainly a BSD-ism.
Brian
> Brian Kolaci writes:
>
> > scandir() and alp
Me too,
I tried replying last night, however the "efilter"
blocked my response.
I use Solaris myself. But its not limited to Solaris.
There would be problems with AIX, IRIX, HP-UX and any
other *real* unix. Major businesses typically *only* use
one of the *real* unix's, go check with Sony, Cit
Hi Ken,
I'd shy away from putting the password in the URL.
What I was thinking was giving the ability of remembering
information in a cookie.
I've been trying to get time to integrate the mysql-limits
api into qmailadmin for this release, but things have been
crazy... I'll see what I can do.
T
OK, I've finally found the time to work on the
qmailadmin-limits API's for file and MySQL based storage.
I've attached the patch for vpopmail 5.3.11, available
at shupp.org.
I've augmented the previous implementation to add the
extra features requested and pretty much implemented what
I stated i
Hi,
I suggest you wait just a bit. I *finally* started working
on the .qmailadmin-limits API's that include *alot* of
other information. I believe this patch does the incorrect
behaviour. The permissions on managers should be configurable,
not hard-coded yes or no (and I disagree with the appr
28 matches
Mail list logo
