After updating Postfix to 2.9.3 the commonly used database type hash does not work anymore. emerge.log: 1345135439: >>> emerge (9 of 27) mail-mta/postfix-2.9.3 to / 1345135440: === (9 of 27) Cleaning (mail-mta/postfix-2.9.3::/usr/portage/mail-mta/postfix/postfix-2.9.3.ebuild) 1345135444: === (9 of 27) Compiling/Merging (mail-mta/postfix-2.9.3::/usr/portage/mail-mta/postfix/postfix-2.9.3.ebuild) 1345136123: === (9 of 27) Merging (mail-mta/postfix-2.9.3::/usr/portage/mail-mta/postfix/postfix-2.9.3.ebuild) 1345136133: >>> AUTOCLEAN: mail-mta/postfix:0 1345136133: === Unmerging... (mail-mta/postfix-2.8.9) 1345136143: >>> unmerge success: mail-mta/postfix-2.8.9 Reproducible: Always Steps to Reproduce: 1. Use a Postfix configuration with alias_maps = hash:/etc/aliases or transport_maps = hash:/etc/postfix/transport or similar. 2. Update a working version < 2.9 with the above configuration to 2.9.3. 3. Watch the Postfixe log file for errors. Actual Results: In the log appear error messages like Aug 26 10:39:07 [postfix/trivial-rewrite] warning: hash:/etc/postfix/transport lookup error for "*" Aug 26 10:39:07 [postfix/trivial-rewrite] warning: hash:/etc/postfix/transport is unavailable. unsupported dictionary type: hash Expected Results: The update should not break the configuration. http://www.postfix.org/DB_README.html
Do not turn off berkdb USE flag is you have hash or btree lookups in your setup. There is a big fat warning in the ebuild output. You should read it.