G'day.
I just hit the same issue, and resolved it instead by using the proxymap
service to allow access from verify in the chroot up to the database in
/var/lib/postfix.
The required changes were:
address_verify_map = proxy:btree:$data_directory/verify_cache
proxy_write_maps =
$smtp_sas
I'm seeing this with 2.7.1-1 although that message from the mailing list
would seem to suggest that the fix should have made it into an upstream
release by now.
Can I suggest this bug is perhaps slightly more important than minor? To
quote the postconf manpage on the verify database, "If the datab
Package: postfix
Version: 2.7.0-1
Severity: minor
Tags: patch
Spurious mail log entry as 'verify_cache.db' is present:
Apr 23 06:02:41 spectre postfix/verify[28696]: close database
/var/lib/postfix/verify_cache.db: No such file or directory
ls -al /var/lib/postfix/
total 40
drwxr-xr-x 2 postfi
3 matches
Mail list logo