Hello,

I thought I should start a new thread, and I will reference:
http://www.mail-archive.com/postfix-users@postfix.org/msg47599.html
http://www.mail-archive.com/postfix-users@postfix.org/msg47590.html (includes postconf -n)

I'm on CentOS 5.8 x86_64 with postfix-2.9.1-1.pcre.sasl2.dovecot.rhel5.x86_64.rpm (custom-built to use LTB LDAP RPM)

Based on infofrom the former thread above, I would expect to see a verify_cache.db at /var/lib/postfix because:

address_verify_cache_cleanup_interval = 12h
address_verify_default_transport = $default_transport
address_verify_local_transport = $local_transport
address_verify_map = btree:$data_directory/verify_cache
address_verify_negative_cache = yes
address_verify_negative_expire_time = 3d
address_verify_negative_refresh_time = 3h
address_verify_poll_count = ${stress?1}${stress:3}
address_verify_poll_delay = 3s
address_verify_positive_expire_time = 31d
address_verify_positive_refresh_time = 7d
address_verify_relay_transport = $relay_transport
address_verify_relayhost = $relayhost
address_verify_sender = $double_bounce_sender
address_verify_sender_dependent_default_transport_maps = $sender_dependent_default_transport_maps address_verify_sender_dependent_relayhost_maps = $sender_dependent_relayhost_maps
address_verify_sender_ttl = 0s
address_verify_service_name = verify
address_verify_transport_maps = $transport_maps
address_verify_virtual_transport = $virtual_transport

but:

   # tree /var/lib/postfix
   /var/lib/postfix
   |-- master.lock
   `-- prng_exch

   0 directories, 2 files

However on other servers(Centos 6.3 with postfix-2.9.4-1.appletech.el6.x86_64.rpm [also custom-built]), it exists.

   # tree /var/lib/postfix/
   /var/lib/postfix/
   |-- master.lock
   |-- postscreen_cache.db
   `-- verify_cache.db

Question1: Is it normal that this file does not exist in our setup (although we use reject_unverified_recipient)?

Q2: If yes, then why, and whatshould we do to enable it? If not, then what may be wrong and how can we correct the situation?

Q3: When verify_cache.db exists, is there a way to view its contents (ina human-readableand useful way) to monitor its behavior?

Thanks,
Nick

Reply via email to