Please read my comments below

Quoting Doug Clements <[EMAIL PROTECTED]>:

> On Tue, Sep 16, 2003 at 10:43:59PM -0700, Tim Hasson wrote:
> > Quoting Doug Clements <[EMAIL PROTECTED]>:
> > 
> > > On Tue, Sep 16, 2003 at 09:17:48PM -0700, Tim Hasson wrote:
> > > > 1. Maildir++ doesn't work on NFS, or at least has serious issues with
> it,
> > > thus 
> > > > breaking the whole quota support thing.
> > > 
> > > Works great here. What problems are you seeing?
> > 
> > Please see my previous post (few hours ago): 
> > Re: Quota problem: negative values in Maildir/maildirsize
> > 
> >
> Gotcha. I misread, thinking you were saying the Maildir++ format was
> problematic on NFS. It appears you mean that the Maildir++ implementation of
> vpopmail is broken. I use maildrop exclusively for delivery to mailboxes, if
> they have quotas or not, which is likely why I see no problems. Maildrop was
> written by Mr Sam, who as far as I know also came up with the Maildir++ spec,
> so I would hope it's a complete implementation.
> Maildir++ violates the spirit of Maildirs in that the maildirsize file that
> keeps track of the quota isn't atomically updatable, like the delivery and
> normal moving around of mail files is and is therefore succeptable to
> corruption when used over NFS sans-locking. In one of the referenced mails
> above, I make the case that this doesn't matter, since the file should be
> rebuilt regularly anyway, and any problems will be minor and corrected as a
> matter of course. 
> You seem to be seeing other things, however.
> It looks possibly like either vdelivermail or the qmail-local patch doesn't
> rebuild the maildirsize file every so often like the Maildir++ spec requires.
> Does anyone know either of these?

True, I noticed the user's having this problem, their maildirsize doesn't just 
contain lots of negative values in them (mostly negatives), but also the size 
of the file 'maildirsize' keeps getting larger and larger and doesn't get 
rebuilt, so the only thing i can do is manually delete it and recreate it.

> > This is not quite desirable..
> That looks like a genuine bug. I don't know why vaddomain would drop
> privilages before creating the directorys and setting appropriate
> permissions. That, or I don't understand how it's supposed to work.

I think it's a design bug because of the permissions on the domains directory 
in ~vpopmail.

I guess vpopmail changes uid/gid before creating the domain directory under 
that uid so that it doesnt have to later do chown/chgrp.

Moreover, if the ~vpopmail/domains directory had world read/write other than 
user/group read/write, qmail would probablly refuse delivering any mail to 
that directory path.

Thoughts, ideas?

> --Doug


Tim Hasson

Reply via email to