http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5751
------- Additional Comments From [EMAIL PROTECTED] 2007-12-18 06:21 ------- I have added some more detailed analysis to the original bug report at https://bugzilla.redhat.com/show_bug.cgi?id=392851 A specific REPRODUCIBLE case of such error is given there. A more general reproducible error case is as follows: On a fresh install, run sa-update with two "--channel" inputs with one corresponding to the base ruleset (e.g., updates.spamassassin.org) but without a valid gpg key and the other (e.g., saupdates.onprotect.com) corresponding to some other supplementary ruleset but with a valid gpg key. The order doesn't seem to matter. Then, sa-update will happily create the /var/lib/spamassassin/3.002003 directory (using Fedora locations) and populate it with the rules from the channel with the valid gpg key while warning of a bad gpg key and failing to add the base ruleset for updates.spamassassin.org. The non-expert user likely won't see/understand/recognize the warning and will be left with a spamassassin configuration without any valid base rules since once the /var/lib/spamassassin/3.002003 directory is created, it overrides the other locations for the original non-updated rules (e.g., /usr/share/spamassassin) Not sure though what the best way to fix this is since technically sa-update is not doing anything wrong. It is only just creating a non-working situation that is obscure to most non-experts :) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
