Hi,
> On Nov 11, 2017, at 7:24 PM, Wietse Venema wrote:
>
> Or you can use 'lmdb:' instead 'btree:'. LMDB support was added in Postfix
> 2.11.
> It's a totally different implementation.
That’s a great idea - that will side-step any Berkeley DB specific bugs.
Thanks,
-
Wietse Venema:
> J Doe:
> > Hi Wietse,
> >
> > > On Nov 11, 2017, at 8:37 AM, Wietse Venema wrote:
> > >
> > > J Doe:
> > >> Is this really the only way to fix this, though ? This feels a bit like
> > >> a workaround as opposed to the ?correct? solution (assuming that
J Doe:
> Hi Wietse,
>
> > On Nov 11, 2017, at 8:37 AM, Wietse Venema wrote:
> >
> > J Doe:
> >> Is this really the only way to fix this, though ? This feels a bit like a
> >> workaround as opposed to the ?correct? solution (assuming that there is a
> >> ?more correct?
Hi Wietse,
> On Nov 11, 2017, at 8:37 AM, Wietse Venema wrote:
>
> J Doe:
>> Is this really the only way to fix this, though ? This feels a bit like a
>> workaround as opposed to the ?correct? solution (assuming that there is a
>> ?more correct? solution).
>
> Why
J Doe:
> Is this really the only way to fix this, though ? This feels a bit like a
> workaround as opposed to the ?correct? solution (assuming that there is a
> ?more correct? solution).
Why bother with all this? The database is synced without error.
It is in a consistent state. Only the close
Hi,
> On Nov 11, 2017, at 3:06 AM, J Doe wrote:
>
> Hello,
>
> I have an admittedly basic question, but I have been trying to troubleshoot
> this for a while with no success.
>
> I have enabled postscreen(8) on Postfix 3.1 and receive a warning in
> mail.log:
>
Hello,
I have an admittedly basic question, but I have been trying to troubleshoot
this for a while with no success.
I have enabled postscreen(8) on Postfix 3.1 and receive a warning in mail.log:
“close database /var/spool/postfix/var/lib/postscreen_cache.db: No such file or
directory