Sieve failure on deliverdb corruption...
Henrique de Moraes Holschuh
hmh at debian.org
Thu Jun 19 09:38:22 EDT 2003
On Thu, 19 Jun 2003, Rob Siemborski wrote:
> On Wed, 18 Jun 2003, Ken Murchison wrote:
> > If we just ignored the fact that deliver.db isn't available, then we'd
> > get people complaining about vacation sending out multiple responses, or
> > the same message being redirected more than once, etc.
> After seeing some of the bad behaviors of db3 if/when a database
> corrupts itself beyond repair today, I've been toying with the idea of
> having lmtpd fatal() if duplicate_init fails to successfully open the
> This, of course, results in no mail being delivered, but its a very
> obvious failure mode that would get the administrator's attention.
I like it. We just need to make sure it outputs a 4xx error if it has
greeted the MTA already, so there is no possibility of mail loss...
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
More information about the Info-cyrus