3.3.0 local.cf parse error
I'm getting the following parse errors after upgrading to 3.3.0: Jan 27 08:04:15.172 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: use_auto_whitelist 1 Jan 27 08:04:15.172 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: user_awl_dsn DBI:mysql:spamassassin Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: user_awl_sql_username amavis Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: user_awl_sql_password spamdb Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: use_dcc 1 I've got two, previously, identical servers setup, one produces these errors with a spamassassin -D --lint command, the other doesn't, the local.cf files are identical, to the point that I've copied the working server's local.cf to the non-working server. Still get the errors. Any ideas why one server would have the errors and the other not? Prior to upgrading, I wasn't getting any errors with 3.2.5... Jeff
Re: 3.3.0 local.cf parse error
On 1/27/2010 11:19 AM, Jackson, Jeff wrote: I'm getting the following parse errors after upgrading to 3.3.0: Jan 27 08:04:15.172 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: use_auto_whitelist 1 Jan 27 08:04:15.172 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: user_awl_dsn DBI:mysql:spamassassin Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: user_awl_sql_username amavis Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: user_awl_sql_password spamdb Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: use_dcc 1 I've got two, previously, identical servers setup, one produces these errors with a spamassassin -D --lint command, the other doesn't, the local.cf files are identical, to the point that I've copied the working server's local.cf to the non-working server. Still get the errors. Any ideas why one server would have the errors and the other not? Prior to upgrading, I wasn't getting any errors with 3.2.5... Jeff Jeff, I believe AWL was changed to be disabled by default in 3.3.0. You may need to uncomment the loadplugin line for AWL in v310.pre.
Re: 3.3.0 local.cf parse error
Jeff, I'm getting the following parse errors after upgrading to 3.3.0: Jan 27 08:04:15.172 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: use_auto_whitelist 1 Jan 27 08:04:15.172 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: user_awl_dsn DBI:mysql:spamassassin Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: user_awl_sql_username amavis Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: user_awl_sql_password spamdb Jan 27 08:04:15.173 [30437] warn: config: failed to parse line, skipping, in /etc/mail/spamassassin/local.cf: use_dcc 1 I've got two, previously, identical servers setup, one produces these errors with a spamassassin -D --lint command, the other doesn't, the local.cf files are identical, to the point that I've copied the working server's local.cf to the non-working server. Still get the errors. Any ideas why one server would have the errors and the other not? Prior to upgrading, I wasn't getting any errors with 3.2.5... You have AWL and DCC plugins disabled, but left their corresponding rules active in your local.cf file. Either enable these two plugins, e.g. by putting in a local.pre the following lines: loadplugin Mail::SpamAssassin::Plugin::AWL loadplugin Mail::SpamAssassin::Plugin::DCC or disable or conditionalize the failing rules, like enclosing them in an ifplugin block: ifplugin Mail::SpamAssassin::Plugin::DCC use_dcc 1 endif ifplugin Mail::SpamAssassin::Plugin::AWL use_auto_whitelist 1 auto_whitelist_factory Mail::SpamAssassin::SQLBasedAddrList user_awl_dsn DBI:mysql:spamassassin user_awl_sql_username amavis user_awl_sql_password spamdb endif The 3.3.0 release notes say: COMPATIBILITY WITH 3.2.5 - as the plugin AWL is no longer loaded by default, to continue using it the following line is needed in one of the .pre files (e.g. local.pre): loadplugin Mail::SpamAssassin::Plugin::AWL Mark