Description of problem: The upgrade process saved the local.cf file, and repaced with a default stub, removing critical site specific settings to protect from excessive spam. Unless there are critical version skew problems with file formats and options, production configuration files should be left in place during an upgrade/update process ... and the new file installed as .rpmnew. Version-Release number of selected component (if applicable): How reproducible: appears always, did for both of our servers. Steps to Reproduce: 1.CDROM upgrade from FC5=>FC6 2. 3. Actual results: spamassassin is cripled by having site specific settings removed. Expected results: upgrade should leave existing configuration files untouched, unless there are compelling changes in file format or options requiring manual intervention after an upgrade/update. Additional info:
The RPM is designed to never replace the local.cf that has been modified. Your problem is not normally reproducible. Are you sure you didn't do an Install instead of Upgrade? That might have screwed it up in this way.
No response, unable to reproduce this problem, closing.