> Macky wrote:
>
> We are thinking to upgrade to the new version of Vpopmail because the
> old one(currently installed vpopmail) has one critical bug in the
> current version we are using needs to be addressed is that mail
> bounces when vdelivermail can't connect to MySQL for whatever reason
> (usually because MySQL is down or busy).
Hmm.. That's an interesting point. If vdelivermail can't retrieve
a users information because it can't connect to the database, it
should cause a deferral. I'll put that on the TODO list.
> and one feature we don't like is the .dir-control file. Can anyone
> explain why it is needed and if we can put the info in the
> .dir-control file in the
> database instead?
You can write some mysql code to do it. If you do, please send me
the patch.
The reason why it is there is because there needs to be an efficent
method for keeping track of the current state of the user directory
layout. And that is needed so a relativily balenced and efficent
user directory tree can be dynamically created as users are added.
And that is needed because putting 100,000 user accounts in one
directory (inode table) is horrendously inefficent.
Yeah ;] write some mysql code to keep track of that and I'll add
it to the next release.
>
> Also, we will soon be implementing NFS storage for our maildirs.
> Meaning: we will have 1 big email storage system and several little
> delivery
> machines mounting the domain directories via NFS. Problem is, what
> happens when the NFS machine is down for whatever reason? Can we patch
> qmail-local
> or vdelivermail to defer delivery if the user's maildir is offline, or
> is this functionality already included somehow w/ qmail?
qmail-local will be doing the delivery into the NFS share, assuming that
your are mounting ~vpopmail/domains on the NFS share. qmail-local should
defer delivery with an error message saying it couldn't change
directory.
Ken Jones
