On 9/14/2018 12:41 PM, Stefan Bauer wrote: > > > 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?
You don't need to do anything other than run newaliases. Postfix will automatically use the changed the aliases map, so reload is unnecessary. The error on closing the database (caused by postfix reload) is an artifact of Berkeley DB and can be ignored; it does no harm. With your environment, you'll likely see that message every time postfix stops or reloads. -- Noel Jones
