Maurizio Caloro:
> Hello
>
> >From time to time I see on mail.log the following error message:
>
> Mar 22 23:29:43 mail postfix/verify[2206]: close database
> /var/lib/postfix/verify_cache.db: No such file or directory (possible
> Berkeley DB bug)
Indeed, the db->c
Hello
>From time to time I see on mail.log the following error message:
Mar 22 23:29:43 mail postfix/verify[2206]: close database
/var/lib/postfix/verify_cache.db: No such file or directory (possible
Berkeley DB bug)
I have see found different answer, but I don't know which in
799]: cache btree:/var/lib/postfix/verify_cache full
> cleanup: retained=2 dropped=0 entries
>
> postfix/verify[16799]: close database /var/lib/postfix/verify_cache.db:
> No such file or directory (possible Berkeley DB bug)
that is normal if you delete the file because normally
it don'
shm...@riseup.net:
>
> when i receive mail from some MTA's (there seems to be no pattern as to
> which ones) and this msg is logged, no STARTTLS is established and i
> receive the mail in the clear
Sorry, verify caches have absolutely nothing to do with TLS encryption.
> the file verify_cache.db
r-- 1 postfix postfix 8192 Sep 26 18:55
/var/lib/postfix/verify_cache.db
postfix/verify[16799]: cache btree:/var/lib/postfix/verify_cache full
cleanup: retained=2 dropped=0 entries
postfix/verify[16799]: close database /var/lib/postfix/verify_cache.db:
No such file or directory (possible Berkeley DB bug)
On 3/10/2011 6:58 AM, Mark Alan wrote:
While using Postfix 2.8.1 + Ubuntu 10.10, after enabling postscreen the
system seems to be working well (sends and receives email without any
apparent problems) but has sporadic errors as shown bellow (without
any other errors or warnings).
This has been
og
Mar 10 11:02:24 mx postfix/postscreen[9697]:
cache /var/lib/postfix/postscreen_cache.db full cleanup: retained=0
dropped=0 entries
Mar 10 11:04:26 mx postfix/postscreen[9697]: close
database /var/lib/postfix/postscreen_cache.db: No such file or
directory (possible Berkeley DB bug)
Mar 10 1
