Re: failed to parse line bayes_path in user_prefs

On 11/21/2014 12:32 PM, Bowie Bailey wrote: > bayes_path is considered to be an administrator setting and is not > allowed to be specified in user_prefs. Ah, that's what I get for grepping through the man page instead of paging through in order. Thanks very much.

Re: failed to parse line bayes_path in user_prefs

n the logs: Nov 21 10:58:31 mail2 spamd[13522]: config: failed to parse line, skipping, in "/home/starchy/.spamassassin/user_prefs": bayes_path /var/spamassassin/bayes_db/bayes Note bayes is a prefix, not a directory. bayes_db and all bayes_ files are chmod 0777. As a side note, I tri

failed to parse line bayes_path in user_prefs

13522]: config: failed to parse line, skipping, in "/home/starchy/.spamassassin/user_prefs": bayes_path /var/spamassassin/bayes_db/bayes Note bayes is a prefix, not a directory. bayes_db and all bayes_ files are chmod 0777. As a side note, I tried working with the default ~/.spamassasin/bayes

Re: warn: config: SpamAssassin failed to parse line, no value provided for "body", skipping: body

:01.084 [10573] warn: config: SpamAssassin failed to parse line, no value provided for "body", skipping: body Feb 16 10:05:01.289 [10573] dbg: config: warning: score set for non-existent rule *RCVD_IN_MSPIKE_WL* I did not change it ;) # grep MSPIKE_WL /etc/spamassassin/local.cf # echo $

Re: warn: config: SpamAssassin failed to parse line, no value provided for "body", skipping: body

Version 3.3.1 on Debian Squeeze -- Dogs are tough. I've been interrogating this one for hours and he still won't tell me who's a good boy. simon@klunky / .co.uk / .org "Kevin A. McGrail" wrote: >On 2/3/2012 5:00 AM, Simon Loewenthal wrote: >> Hi, >> >> I have an error somewhere in

Re: warn: config: SpamAssassin failed to parse line, no value provided for "body", skipping: body

On 2/3/2012 5:00 AM, Simon Loewenthal wrote: Hi, I have an error somewhere in a rule (not that I have added one for ages so I cannot fathom how it slipped in). The error message from -D --lint is listed below. I do not know if these RCVD_IN rules are related. I have not referenced th

warn: config: SpamAssassin failed to parse line, no value provided for "body", skipping: body

body in the local.cf. Feb 3 10:38:49.782 [6592] dbg: plugin: loading ClamAV from /etc/spamassassin/clamav.pm Feb 3 10:38:49.793 [6592] dbg: plugin: did not register Mail::SpamAssassin::Plugin::Rule2XSBody, already registered Feb 3 10:38:50.121 [6592] warn: config: SpamAssassin failed to parse

Re: sa-updates failures since few days : failed to parse line URIBL_SBL_A

On 12/12/2011 6:17 AM, numberxiii wrote: Hi We encountered a problem with sa-update since the last week-end. It fails with this error : config: failed to parse line, skipping, in "/tmp/.spamassassin32504f7H7V4tmp/72_active.cf": uridnsblURIBL_SBL_A sbl.spamhaus.org. A M

sa-updates failures since few days : failed to parse line URIBL_SBL_A

Hi We encountered a problem with sa-update since the last week-end. It fails with this error : config: failed to parse line, skipping, in "/tmp/.spamassassin32504f7H7V4tmp/72_active.cf": uridnsblURIBL_SBL_A sbl.spamhaus.org. A May be it's related to : https://is

Re: Re : failed to parse line

On 12/6/2011 12:55 PM, Christian Gregoire wrote: What happens if you put those lines into a local.cf or similar configuration file rather than a user preference? Doesn't look like it's taken into account. The rule is not triggered Then you are putting it in the wrong place or the rule isn't hi

Re : failed to parse line

>What happens if you put those lines into a local.cf or similar configuration >file rather than a user preference? Doesn't look like it's taken into account. The rule is not triggered >What are your command line parameters for spamd and spamc? /usr/bin/spamd --socketpath=/tmp/spamassassin.sock

Re: failed to parse line

:20 webmail-9 spamd[21374]: spamd: using default config for christ...@.fr: /var/atmail/users/christ...@.fr/user_prefs Dec 6 14:39:20 webmail-9 spamd[21374]: config: failed to parse line, skipping, in "/var/atmail/users/christ...@.fr/user_prefs": header LOCAL_DEMONSTRATI

failed to parse line

config for christ...@.fr: /var/atmail/users/christ...@.fr/user_prefs   Dec  6 14:39:20 webmail-9 spamd[21374]: config: failed to parse line, skipping, in "/var/atmail/users/christ...@.fr/user_prefs": header LOCAL_DEMONSTRATION_SUBJECT Subject =~ /\btest\b/i   Dec  6 14:39:20

Re: Failed to parse line in 60_adsp_override_dkim.cf

Jeffrey, > I'm running SpamAssassin version 3.3.1, running on Perl version 5.10.0. > I'm seeing a lot of errors similar to: > > config: failed to parse line, skipping, in > "/tmp/.spamassassin13924v0B7j5tmp/60_adsp_override_dkim.cf": > adsp_override ebay.com

Failed to parse line in 60_adsp_override_dkim.cf

I'm running SpamAssassin version 3.3.1, running on Perl version 5.10.0. I'm seeing a lot of errors similar to: config: failed to parse line, skipping, in "/tmp/.spamassassin13924v0B7j5tmp/60_adsp_override_dkim.cf": adsp_override ebay.com during the daily cron run. (

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

ram wrote: > > > On Wed, May 5, 2010 at 6:49 PM, Bowie Bailey > wrote: > > ram wrote: > > > > i still see this errors > > > > May 5 10:28:03.484 [3153] dbg: config: warning: score set for > > non-existent rule SHORTCIRCUIT > > May 5 10:28:

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On Sun, May 9, 2010 at 1:03 AM, Benny Pedersen wrote: > On lør 08 maj 2010 16:38:58 CEST, ram wrote > > > User-Agent: Internet Messaging Program (IMP) 3.2.5 >> > > un updated webmail > what is that means ? Ram,

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On lør 08 maj 2010 16:38:58 CEST, ram wrote User-Agent: Internet Messaging Program (IMP) 3.2.5 un updated webmail -- xpoint http://www.unicom.com/pw/reply-to-harmful.html

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On Wed, May 5, 2010 at 6:49 PM, Bowie Bailey wrote: > ram wrote: > > > > i still see this errors > > > > May 5 10:28:03.484 [3153] dbg: config: warning: score set for > > non-existent rule SHORTCIRCUIT > > May 5 10:28:03.485 [3153] dbg: config: warning: score set for > > non-existent rule SUBJ_

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

ram wrote: > > i still see this errors > > May 5 10:28:03.484 [3153] dbg: config: warning: score set for > non-existent rule SHORTCIRCUIT > May 5 10:28:03.485 [3153] dbg: config: warning: score set for > non-existent rule SUBJ_RE_NUM > May 5 10:28:03.485 [3153] dbg: config: warning: score set

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On Mon, May 3, 2010 at 7:28 PM, Benny Pedersen wrote: > On man 03 maj 2010 07:51:01 CEST, ram wrote > > this is my output >> > > super > > > May 3 11:19:22.416 [621] warn: config: failed to parse line, skipping, in > "/etc/mail/spamassassin/local.cf&

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On man 03 maj 2010 07:51:01 CEST, ram wrote this is my output super May 3 11:19:22.416 [621] warn: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1 remove that "use_auto_whitelist" line in local.cf more in

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On Mon, 2010-05-03 at 11:21 +0530, ram wrote: > this is my output One line extracted from the debug output. > May 3 11:19:22.416 [621] warn: config: failed to parse line, skipping, > in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1 I believe it has been mentioned be

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On fre 30 apr 2010 06:21:18 CEST, ram wrote warn: lint: 1 issues detected, please rerun with debug enabled for more information what is it ? you already see the problem in that line press s in less to save the whole output if unsure what to do, and then pastebin it on a webpage and then pos

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On fre 30 apr 2010 06:21:18 CEST, ram wrote warn: lint: 1 issues detected, please rerun with debug enabled for more information what is it ? you already see the problem in that line press s in less to save the whole output if unsure what to do, and then pastebin it on a webpage and then pos

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On Wed, Apr 28, 2010 at 10:11 PM, Benny Pedersen wrote: > On ons 28 apr 2010 10:55:10 CEST, ram wrote > > > /usr/bin/spamd -V >> SpamAssassin Server version 3.3.1 >> running on Perl 5.8.8 >> with SSL support (IO::Socket::SSL 1.01) >> with zlib support (Compress::Zlib 1.42) >> > > spamassassin

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On ons 28 apr 2010 10:55:10 CEST, ram wrote /usr/bin/spamd -V SpamAssassin Server version 3.3.1 running on Perl 5.8.8 with SSL support (IO::Socket::SSL 1.01) with zlib support (Compress::Zlib 1.42) spamassassin 2>&1 -D --lint | less see what gets loaded where -- xpoint http://www.unic

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On ons 28 apr 2010 10:54:38 CEST, ram wrote both installed from rpm so you really have both installed at once ? -- xpoint http://www.unicom.com/pw/reply-to-harmful.html

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On ons 28 apr 2010 08:10:49 CEST, ram wrote after update also still it shows old version why ? make sure its not installed so possible you have 2 perl versions, 2 spamassassin versions installed only you can see it -- xpoint http://www.unicom.com/pw/reply-to-harmful.html

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

ram wrote: > /usr/bin/spamd -V > SpamAssassin Server version 3.3.1 > running on Perl 5.8.8 > with SSL support (IO::Socket::SSL 1.01) > with zlib support (Compress::Zlib 1.42) > > > On Wed, Apr 28, 2010 at 12:14 PM, Jari Fredriksson > wrote: > > On 28.4.2010 9:10, ra

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

/usr/bin/spamd -V SpamAssassin Server version 3.3.1 running on Perl 5.8.8 with SSL support (IO::Socket::SSL 1.01) with zlib support (Compress::Zlib 1.42) On Wed, Apr 28, 2010 at 12:14 PM, Jari Fredriksson wrote: > On 28.4.2010 9:10, ram wrote: > > after update also still it shows old ver

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

both installed from rpm Ram On Wed, Apr 28, 2010 at 12:14 PM, Jari Fredriksson wrote: > On 28.4.2010 9:10, ram wrote: > > after update also still it shows old version why ? > > > > X-Spam-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_00, > > DATE_IN_PAST_03_06,HTML_MESSAGE,HTML_MIME_NO_H

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

On 28.4.2010 9:10, ram wrote: > after update also still it shows old version why ? > > X-Spam-Status: No, score=-0.4 required=5.0 tests=AWL,BAYES_00, > DATE_IN_PAST_03_06,HTML_MESSAGE,HTML_MIME_NO_HTML_TAG,MIME_HTML_ONLY, > RCVD_IN_SORBS_WEB autolearn=no version=3.2.5 > Maybe you used to use

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

to 3.3.X >> > >> > when i restart i get this message >> > >> > spamd[18549]: config: failed to parse line, skipping, in >> > "/etc/mail/spamassassin/local.cf <http://local.cf>": use_auto_whitelist >> 1 >> > any suggestions &

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

message > > > > spamd[18549]: config: failed to parse line, skipping, in > > "/etc/mail/spamassassin/local.cf <http://local.cf>": use_auto_whitelist > 1 > > any suggestions > > > > Ram > > As far as I remember the AWL plugin is not loaded by de

Re: spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

ram schrieb: > Hi > > i have recently update from 3.2.X to 3.3.X > > when i restart i get this message > > spamd[18549]: config: failed to parse line, skipping, in > "/etc/mail/spamassassin/local.cf <http://local.cf>": use_auto_whitelist 1 > any

spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1

Hi i have recently update from 3.2.X to 3.3.X when i restart i get this message spamd[18549]: config: failed to parse line, skipping, in "/etc/mail/spamassassin/local.cf": use_auto_whitelist 1 any suggestions Ram

Re: config: failed to parse line

Micah Anderson wrote: Occasionally I am seeing the following log lines, they don't seem to be fatal, but I'd like to know what they are so I can decide if I need to fix something: Sep 21 07:24:07 spamd2 spamd[7749]: config: failed to parse line, skipping, in "(no file)": x

config: failed to parse line

Occasionally I am seeing the following log lines, they don't seem to be fatal, but I'd like to know what they are so I can decide if I need to fix something: Sep 21 07:24:07 spamd2 spamd[7749]: config: failed to parse line, skipping, in "(no file)": x-train Sep 21 07:24:

RE: --lint reports "failed to parse line, skipping: _ _2_ _R_TEXT_"; can't find the problem

> it turns out that there was a hidden file in the same > directory as my "local.cf" named, > > "._local.cf" > > filled with garbage, which the --lint was loading/reading. > > deleting it makes the --lint failure go away. This looks like the type of hidden files Apple computers leave

Re: --lint reports "failed to parse line, skipping: _ _2_ _R_TEXT_"; can't find the problem

> [7718] warn: config: failed to parse line, skipping: _ _2_ _R_TEXT_ No idea what that's about. The underscores could be other random/non-print chars btw. it turns out that there was a hidden file in the same directory as my "local.cf" named, "._local.c

Re: --lint reports "failed to parse line, skipping: _ _2_ _R_TEXT_"; can't find the problem

On Thu, Dec 21, 2006 at 08:46:24AM -0800, snowcrash+spamassassin wrote: > [7718] dbg: plugin: fixed relative path: > /etc/mail/spamassassin/updates/3.001008/updates_spamassassin_org/80_additional.cf /etc/mail/spamassassin/updates ? > [7718] warn: config: failed to p

--lint reports "failed to parse line, skipping: _ _2_ _R_TEXT_"; can't find the problem

[7718] warn: config: failed to parse line, skipping: _ _2_ _R_TEXT_ but, > cd /etc/mail/spamassassin/updates/3.001008/updates_spamassassin_org > ls 80_additional.cf 80_additional.cf > grep -i R_TEXT 80_additional.cf > and, even

Re: Failed to parse line...

Drew Burchett wrote: > I made this same mistake yesterday.  Turned out that I hadn’t enabled razor in v310.pre.   Thanks very much for the reply Drew!   I found that the line loading the Razor plug-in in v310.pre was commented out:   # Razor2 - perform Razor2 message checks. # # Ra

Failed to parse line...

fo: config: failed to parse line, skipping: razor_config /var/amavis/.razor/razor-agent.conf [7670] dbg: plugin: Mail::SpamAssassin::Plugin::ReplaceTags=HASH(0x8edd2c0) implements 'finish_parsing_end' /var/amavis directory, subdirectories and all files are owned by user and group amavis and

Re: local.cf: failed to parse line

--- Michael Monnerie <[EMAIL PROTECTED]> wrote: > On Sonntag, 4. Dezember 2005 19:05 Peter wrote: > > [12981] info: config: failed to parse line, skipping: > > use_auto_whitelist 1 [12981] info: config: failed to parse line, > > skipping: use_razor2 1 [12981] info: c

Re: local.cf: failed to parse line

At 01:05 PM 12/4/2005, Peter wrote: Hi. Yesterday I installed SA 3.1.0 by Perl module. I am using it with amavisd-new 2.3.3. I am getting these messages when I start amavisd-new: [12981] info: config: failed to parse line, skipping: use_auto_whitelist 1 [12981] info: config: failed to parse

Re: local.cf: failed to parse line

On Sonntag, 4. Dezember 2005 19:05 Peter wrote: > [12981] info: config: failed to parse line, skipping: > use_auto_whitelist 1 [12981] info: config: failed to parse line, > skipping: use_razor2 1 [12981] info: config: failed to parse line, > skipping: use_dcc 1 [12981] info: confi

local.cf: failed to parse line

Hi. Yesterday I installed SA 3.1.0 by Perl module. I am using it with amavisd-new 2.3.3. I am getting these messages when I start amavisd-new: [12981] info: config: failed to parse line, skipping: use_auto_whitelist 1 [12981] info: config: failed to parse line, skipping: use_razor2 1 [12981

Re: SpamAssassin failed to parse line, skipping?

Theo Van Dinter kluge.net> writes: > > On Tue, Nov 23, 2004 at 11:42:09AM -0800, Henry Kwan wrote: > > [root beans Mail-SpamAssassin-3.0.1]# spamassassin --lint > > config: SpamAssassin failed to parse line, skipping: num_check_received 5 > > lint: 1 issues detecte

Re: SpamAssassin failed to parse line, skipping?

On Tue, Nov 23, 2004 at 11:42:09AM -0800, Henry Kwan wrote: > [EMAIL PROTECTED] Mail-SpamAssassin-3.0.1]# spamassassin --lint > config: SpamAssassin failed to parse line, skipping: num_check_received 5 > lint: 1 issues detected. please rerun with debug enabled for more > informat

SpamAssassin failed to parse line, skipping?

Hi. Just upgraded from 2.64 to 3.01 and everything seems to working fine except that --lint gives me one error: [EMAIL PROTECTED] Mail-SpamAssassin-3.0.1]# spamassassin --lint config: SpamAssassin failed to parse line, skipping: num_check_received 5 lint: 1 issues detected. please rerun with