https://bugs.exim.org/show_bug.cgi?id=2206
--- Comment #13 from Phil Pennock <[email protected]> --- Suggestion: 1. Stop Exim 2. Use db_recover from the old version if you still have it; either as the exim runtime user, or chown the files in the spool DB area `$(exim -n -bP spool_directory)/db` to the exim runtime user 3. Use db_recover from the new DB version; same ownership issues 4. Start Exim If that fails: 1. Stop Exim 2. Remove all the files inside `$(exim -n -bP spool_directory)/db` -- they're an optimization and can be re-built 3. Start Exim If that fails, then the newest BDB from Oracle is not able to maintain an internally-consistent DB environment with the API used by Exim and is thus incompatible with Exim, by default. If you know BDB well, then you _might_ be able to craft a `DB_CONFIG` file which you can manually place inside the spool area, to get things working, but since Exim won't create/manage that for you, it's a little fragile. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
