Re: X-Spam-Status different info
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
Re: X-Spam-Status different info
Gabriel Millerd wrote: 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. You could never put your loadplugin lines for plugins included with SA in cf files (in your local site config dir) without screwing up rules included with SA that depend on those plugins. 3.2 makes this breakage more visible due to a missing Check plugin causing SA to abort. 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. Properly configured (loadplugin lines in pre file(s)), you shouldn't have to juggle anything around. the \d+_scores.cf rules also can be a pain with sa-update which is a big part of the juggling. Care to elaborate? Daryl
Re: X-Spam-Status different info
On 5/11/07, Daryl C. W. O'Shea [EMAIL PROTECTED] wrote: the \d+_scores.cf rules also can be a pain with sa-update which is a big part of the juggling. Care to elaborate? If you have a minimal configuration the mass-check scores will likely bomb on your lint check. The names of the two plugins escape me, I believe its a the uri scanning and dnsbl one. Which later in those same files have ifplugin/endif lines wrapping similar rule scores. * I was merely pointing out that the switch from pre-3.2 to 3.2 is just stricter. In 3.1.8 you could can / run with an all in one local.cf and no other file in /etc/mail/spamassassin and let sa-update or re/sare script do their thing and they would march on. The conversion issues from pre-3.2 to 3.2 such as the no loaded plugin implements 'check_main': cannot scan and the why are my options being ignored from users I would guess may indicate this. The README snippet below and the lines in the /etc/mail/spamassassin default files that reads may not be as clear or easily over looked. Especially since I think the M:S:Conf does not mention this .cf/.pre distinction. # This is the right place to customize your installation of SpamAssassin. # # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be # tweaked. - /usr/share/spamassassin/*.cf: Distributed configuration files, with all defaults. Do not modify these, as they are overwritten when you upgrade. - /etc/mail/spamassassin/*.cf: Site config files, for system admins to create, modify, and add local rules and scores to. Modifications here will be appended to the config loaded from the above directory. - /etc/mail/spamassassin/*.pre: Plugin control files, installed from the distribution. These are used to control what plugins are loaded. Modifications here will be loaded before any configuration loaded from the above directories. You want to modify these files if you want to load additional plugins, or inhibit loading a plugin that is enabled by default. If the files exist in /etc/mail/spamassassin, they will not be overwritten during future installs. -- Gabriel Millerd
