I don't mind doing some coding, but there seems to
be more missing. I'll need to dig through the code
some more. It would be nice if we can have the
postmaster get an unlimited quota so they can be
informed that their domain is over quota and that
they should get the quota increased or have their
people start cleaning up their mail. The postmaster
may need to get mail on each bounce (not the message,
but that a message from so-and-so bounced), and possibly
which ID's are using up the space so it can be cleaned
properly.
Before putting some code together, we may want to put
together a real design first and try to think it through.
The domain per unix ID is good, but we may want to put
the postmaster in a different place so they can still
get notifications.
What are your thoughts? What else did I miss? (I'm sure
I've missed alot).
Thanks,
Brian
> Mailing-List: contact [EMAIL PROTECTED]; run by ezmlm
> Delivered-To: mailing list [EMAIL PROTECTED]
> Date: Fri, 13 Oct 2000 17:08:08 -0500
> From: Ken Jones <[EMAIL PROTECTED]>
> To: Brian Kolaci <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> Subject: Re: quota question on 4.9.5
>
> Brian Kolaci wrote:
> >
> > Hi,
> >
> > I have a quota question...
> > I'd like to put "per domain" quotas using
> > the O/S disk quotas, and use a separate uid/gid.
> > I noticed in vdelivermail.c that each of
> > the write() calls check for failure and return
> > a temporary failure. Shouldn't there be a check
> > for EDQUOT and bounce the message if the user
> > exceeded their quota?
> >
> > Thanks,
> >
> > Brian
>
> Good point. Feel like putting together some code for that?
>
> Ken Jones
