Re: bug: postconf keys have default "btree" values when no BDB support is compiled in
Quanah Gibson-Mount: > When building Postfix with zero support for BDB, two postconf keys still > end up with default btree values: > > address_verify_map = btree:$data_directory/verify_cache > postscreen_cache_map = btree:$data_directory/postscreen_cache It is configurable, and it is up to you choose one of the two dozen database types that are supported. If you don't like that, then you can provide a source code and documentation patch. Wietse
bug: postconf keys have default "btree" values when no BDB support is compiled in
When building Postfix with zero support for BDB, two postconf keys still end up with default btree values: address_verify_map = btree:$data_directory/verify_cache postscreen_cache_map = btree:$data_directory/postscreen_cache This seems to be invalid, as any attempt to enable their usage will result in automatic failure (This issue was raised by one of our clients who ran into this problem after enabling address_verify_map be used). I would think the default values should not include unsupported database formats. --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. Zimbra :: the leader in open source messaging and collaboration
