Stefan Bauer:
> Am Freitag, 14. September 2018 schrieb Wietse Venema :
> > Stefan Bauer:
> >> verify_cache.db seems to get corrupted or at least not updated properly
> as
> >> new/updated entries do not get correctly verified and postfix logs:
> >>
> >> close database /var/lib/postfix/verify_cache.db: No such file or
> directory
> >> > (possible Berkeley DB bug
> >
> > That is logged after 'postfix reload", and until now has not been
> > a problem. The warnming is logged just to be sure, because people
> > keep imprving Berkeley DB.
> >
> >> only a postfix stop, rm verify_cache* , postfix start helps.
> >
> > That is complete and utter overkill.
>
> so what else is recommended to update the db to have recent data?
Perhaps use the configurable features to control caching of 'negative'
results:
address_verify_negative_cache = yes
address_verify_negative_expire_time = 3d
address_verify_negative_refresh_time = 3h
The 'negative' results are cached to avoid overloading the server
with address verify messages.
I guess that some people can wait for 5 minutes until the negative
cache result has expired?
Wietse
