On Thursday 06 March 2003 14:15, Brian Kolaci wrote:
>   > So the domain quotas aren't stored in a file, but rather in whatever


> Good luck trying to get everyone to swap to a file based system.
> I personally like *everything* in the database rather than filesystem.
> All the information (other than message store & cache info) is in the
> database for easy backup/recovery.

Could you clarify something for me?

If vpopmail stores the actual user quota in a database, and the maildirsize
file just stores the current size of the maildir (which IS a file based
system, BTW), then doesn't that mean that Maildrop has NEVER been capable
of enforcing maildir++ with vpopmail?

All of the docs on the web seem to suggest that maildrop IS compatible with
maildir++. Does "compatible" in that sense only mean that maildrop can
manipulate the maildirsize file? But that it doesn't actually have a clue
when a user's quota is exceeded? I guess I never understood that properly.

Also, I don't see why implementing "soft" quotas with another file inside
the maildir would be such a bad idea. The maildirsize file is already
vulnerable to user modification, so it ONLY works when the user doesn't
have shell access to their own maildir. Also, EMAIL is backed up from the
file system, so what's wrong with backing up the quota that applies to that
email with it?

> I'd say we beat this topic to death though.  Since you're using
> maildrop, then why not create a patch for it.  Then the patch itself
> could be included in the vpopmail distribution, or kept separate as
> its own distribution.

Sure, I could do that, but then I'd have to maintain a patch, and that's
messy. I'd much rather implement a standard that everyone can work with.

Please bare with me here. I'm starting to realize that I didn't really
understand how these quotas work, and that there is a great possibility
that maildrop was never really capable of enforcing maildir++ quotas
(because maildir++ doesn't really have much to do with the quota itself,
but rather the size of the maildir)

I really need a way to filter email on the server side, so unless that
functionality makes it's way into vdelivermail in the near future, I'd
really like to discuss the possibility of expanding the maildir++
specification to include user and domain quotas.

I'd be willing to write code for this too, so it's not like you're talking
to someone who's just mouthing off and whining for functionality. This
is how Open Source works: When a developer has an itch, he scratches it,
and everyone benefits, right?

Lets talk. If you're willing to help me hammer out an idea that works,
then I'll pitch it to Mr. Sam. If we do a good job and it makes sense,
then I doubt he'll object as long as I do most of the coding and he
doesn't have to.

> Brian

Jesse Guardiani, Systems Administrator
WingNET Internet Services,
P.O. Box 2605 // Cleveland, TN 37320-2605
423-559-LINK (v)  423-559-5145 (f)

We are actively looking for companies that do a lot of long
distance faxing and want to cut their long distance bill by
up to 50%.  Contact [EMAIL PROTECTED] for more info.

Reply via email to