In v3.2 it seems the reading of the /etc/mail/spamassassin/*.(pre|cf) files is less forgiving. You used to be able to have the all in one .cf file before v3.2. Likely your header rules are in a .cf file and the sa-update is just reading the .pre file.
I had to juggle the /etc/mail/spamassassin files around quite a bit to get both spamd and sa-update to work. "script -c "sa-update -D" /tmp/sa.log" is your friend. the "\d+_scores.cf" rules also can be a pain with sa-update which is a big part of the juggling. On 5/11/07, Patrick Slokker <[EMAIL PROTECTED]> wrote:
-----Oorspronkelijk bericht----- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Verzonden: vrijdag 11 mei 2007 23:01 Aan: users@spamassassin.apache.org Onderwerp: RE: SA Rules Auto-Update ? ----- Original Message ----- >Most common usage is: > > $ sa-update > >Or, if you want to see what it's doing: > > $ sa-update -D Hello, After a Spamassassin update from 3.1.5 to 3.2.0 my Spam reports are different. in 3.1.5: X-Spam-Checker-Version: SpamAssassin 3.1.5 (2006-08-29) X-Spam-Level: X-Spam-Status: No, score=-2.6 required=2.9 tests=BAYES_00 autolearn=ham version=3.1.5 now it is: X-Spam-Checker-Version: SpamAssassin 3.2.0 (2007-05-01) X-Spam-Report: * 1.0 MIME_QP_LONG_LINE RAW: MIME_QP_LONG_LINE * 1.9 SARE_OEM_POP_PRICES3 SARE_OEM_POP_PRICES3 * 0.8 SARE_OEM_PRODS_1 SARE_OEM_PRODS_1 * 0.9 SARE_OEM_PRODS_FEW SARE_OEM_PRODS_FEW * 0.9 SARE_PRODUCTS_03 SARE_PRODUCTS_03 * 0.4 SARE_PRODUCTS_02 SARE_PRODUCTS_02 * 1.3 SARE_OEM_AND_OTHER SARE_OEM_AND_OTHER My procmail.rc is checking on X-Spam-Status: Yes How can I set the message header back as it was in version 3.1.5 Regards Patrick Slokker
-- Gabriel Millerd
