>
> Sounds good. I was hoping to stay away from domain based
> quotas outside of the file system controls, and just let
> the file system handle that for us.
>
> I like the bounce message idea of coming from the virtual
> domain. That's a good one ;)
>
> When it's ready, se
syjne Krzysztof Dabrowski [mailto:[EMAIL PROTECTED]]
Sent: Sunday, October 15, 2000 2:42 PM
To: [EMAIL PROTECTED]
Subject: Re: quota question on 4.9.5
>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 woul
>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 ha
> 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]
> Subjec
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
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
