Nopes still didn't work out...seems totally wild... haha.. :)
anyway, I will try reinstalling.... Thank you for your valuable
time..
----- Original Message -----
From: "jdow" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 11, 2004 10:21 AM
Subject: Re: Log Error
> I am sorry about the acerbity. However I note that the line just above:
> > # score SYMBOLIC_TEST_NAME n.nn
> Now, I'm not aware that SpamAssassin can use a symbolic value for a
> test score, particularly one in the format "n.nn". What happens if
> you change it to "0.01" instead of "n.nn"?
> {^_^}
> ----- Original Message -----
> From: "Binaya" <[EMAIL PROTECTED]>
> To: "jdow" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Monday, 2004 May, 10 19:25
> Subject: Re: Log Error
>
>
> > Dear Jdow,
> > I do appreciate your feedback and your patience :) . I can
> > understand it . But the main problem is the line no. 28 of "user_prefs"
> of
> > ~root/.spamassassin directory is a blank line...
> >
> > I deleted that blank line and tried againt too.. Still the same error
> > message.
> >
> > I am attaching the error message that I got when I ran the command
> > spamassassin -lint -D . It is as below
> >
> >
> > [EMAIL PROTECTED] .spamassassin]# /usr/bin/spamassassin --lint -D
> > debug: ignore: using a test message to lint rules
> > debug: using "/usr/share/spamassassin" for default rules dir
> > debug: using "/etc/mail/spamassassin" for site rules dir
> > debug: using "/root/.spamassassin" for user state dir
> > debug: using "/root/.spamassassin/user_prefs" for user prefs file
> > debug: is Net::DNS::Resolver unavailable? 0
> > debug: trying (3) google.com...
> > debug: looking up MX for 'google.com'
> > debug: MX for 'google.com' exists? 1
> > debug: MX lookup of google.com succeeded => Dns available (set
> dns_available
> > to hardcode)
> > debug: is DNS available? 1
> > debug: running header regexp tests; score so far=0
> > debug: running body-text per-line regexp tests; score so far=3.1
> > debug: check_for_very_long_text: found 1350 bytes
> > debug: check_for_very_long_text: found 1350 bytes
> > debug: spam-phrase score: 32.7734170591313: hits: this message
> > debug: running raw-body-text per-line regexp tests; score so far=5
> > debug: running uri tests; score so far=5
> > debug: uri tests: Done uriRE
> > debug: running full-text regexp tests; score so far=5
> > debug: Razor2 is not available
> > debug: DCC is not available: dccproc not found
> > debug: Razor1 is not available
> > debug: Pyzor is not available: pyzor not found
> > debug: running meta tests; score so far=6
> > Scalar found where operator expected at (eval 14) line 28, near "}
$self"
> > (Missing operator before $self?)
> > Failed to run header SpamAssassin tests, skipping some: syntax error at
> > (eval 14) line 28, near "} $self"
> >
> > debug: is spam? score=6 required=5
> >
>
tests=DATE_MISSING,INVALID_MSGID,MISSING_HEADERS,NO_REAL_NAME,SPAM_PHRASE_21
> > _34,SUBJ_MISSING,SUPERLONG_LINE
> >
> >
> >
> > Also my user_prefs file of ~root/.spamassassin is as below:
> > -----------------------------------------------------------------
> >
> >
> >
> > # SpamAssassin user preferences file. See 'man
Mail::SpamAssassin::Conf'
> > for
> > # details of what can be tweaked.
> > #*
> > #* Note: this file is not read by SpamAssassin until copied into the
user
> > #* directory. At runtime, if a user has no preferences in their home
> > directory
> > #* already, it will be copied for them, allowing them to perform
> > personalised
> > #* customisation. If you want to make changes to the site-wide
defaults,
> > #* create a file in /etc/spamassassin or /etc/mail/spamassassin instead.
> >
>
###########################################################################
> >
> > # How many hits before a mail is considered spam.
> > required_hits 5
> >
> > # Whitelist and blacklist addresses are now file-glob-style patterns, so
> > # "[EMAIL PROTECTED]", "[EMAIL PROTECTED]", or "*.domain.net" will all work.
> > # whitelist_from [EMAIL PROTECTED]
> >
> > # Add your own customised scores for some tests below. The default
scores
> > are
> > # read from the installed spamassassin rules files, but you can override
> > them
> > # here. To see the list of tests and their default scores, go to
> > # http://spamassassin.org/tests.html .
> > #
> > # score SYMBOLIC_TEST_NAME n.nn
> > ( this comes out to be line no. 28)
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "jdow" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, May 10, 2004 3:53 PM
> > Subject: Re: Log Error
> >
> >
> > > I have told you twice already. This makes the third time.
> > >
> > > l
> > > IT IS IN THIS FILE: "/root/.spamassassin/user_prefs"
> > >
> > >
> > > IT IS AT LINE 28.
> > >
> > > That is precisely what the debugging information tells you.
> > >
> > > {^_^}
> > >
> > > ----- Original Message -----
> > > From: "Binaya" <[EMAIL PROTECTED]>
> > > To: "jdow" <[EMAIL PROTECTED]>;
> <[EMAIL PROTECTED]>
> > > Sent: Sunday, 2004 May, 09 22:59
> > > Subject: Re: Log Error
> > >
> > >
> > > > but the mail problem is i cannot figure it out in which file line
no.
> 28
> > > has
> > > > error :)
> > > >
> > > >
> > > > ----- Original Message -----
> > > > From: "jdow" <[EMAIL PROTECTED]>
> > > > To: <[EMAIL PROTECTED]>
> > > > Sent: Monday, May 10, 2004 9:43 AM
> > > > Subject: Re: Log Error
> > > >
> > > >
> > > > > In the messages below:
> > > > >
> > > > > > Created user preferences file: /root/.spamassassin/user_prefs
> > > > > This tells you which file was bad,
"/root/.spamassassin/user_prefs"
> > > > >
> > > > > > Scalar found where operator expected at (eval 14) line 28, near
"}
> > > > $self"
> > > > > > (Missing operator before $self?)
> > > > > Those lines tell you it was on line 28 and the type of error.
> Without
> > > > > that line and a little context around it further help cannot be
> > > proffered.
> > > > >
> > > > > {^_^}
> > > > > ----- Original Message -----
> > > > > From: "Binaya" <[EMAIL PROTECTED]>
> > > > > To: "Matthias Fuhrmann" <[EMAIL PROTECTED]>;
> > > > > <[EMAIL PROTECTED]>
> > > > > Sent: Sunday, 2004 May, 09 20:15
> > > > > Subject: Re: Log Error
> > > > >
> > > > >
> > > > > > Dear Fuhrmann,
> > > > > > Thanks for the response. Well I got the following error
> > > message
> > > > > when
> > > > > > I ran spamassassin --linit
> > > > > >
> > > > > > [EMAIL PROTECTED] root]# /usr/bin/spamassassin --lint
> > > > > >
> > > > > > Created user preferences file: /root/.spamassassin/user_prefs
> > > > > > Scalar found where operator expected at (eval 14) line 28, near
"}
> > > > $self"
> > > > > > (Missing operator before $self?)
> > > > > > Failed to run header SpamAssassin tests, skipping some: syntax
> error
> > > at
> > > > > > (eval 14) line 28, near "} $self"
> > > > > >
> > > > > >
> > > > > > Where should I check for more info ?
> > > > > >
> > > > > > Thanking you.
> > > > > >
> > > > > >
> > > > > >
> > > > > > ----- Original Message -----
> > > > > > From: "Matthias Fuhrmann"
<[EMAIL PROTECTED]>
> > > > > > To: <[EMAIL PROTECTED]>
> > > > > > Sent: Monday, May 10, 2004 12:26 AM
> > > > > > Subject: Re: Log Error
> > > > > >
> > > > > >
> > > > > > > On Sun, 9 May 2004, Binaya wrote:
> > > > > > >
> > > > > > > > Dear all,
> > > > > > > >
> > > > > > > > I am running spamassassin 2.44 in my Red Hat Linux
> 9.0
> > > > > machine
> > > > > > > > which is running sendmail. I have seen some errors in it
which
> > is
> > > as
> > > > > > below.
> > > > > > > > Will anyone please let me know what may be going wrong and
> which
> > > > file
> > > > > > should
> > > > > > > > I check for more information. ?
> > > > > > > >
> > > > > > > > May 9 13:52:50 kopila spamd[29726]: Scalar found where
> operator
> > > > > > expected at
> > > > > > > > (eval 24) line 28, near "} $self"
> > > > > > > > May 9 13:52:50 kopila spamd[29726]: ^I(Missing operator
> before
> > > > > $self?)
> > > > > > > > May 9 13:52:50 kopila spamd[29726]: Failed to run header
> > > > SpamAssassin
> > > > > > > > tests, skipping some: syntax error at (eval 24) line 28,
near
> "}
> > > > > $self"
> > > > > > >
> > > > > > > never seen those error, but try using spamd with option -D (
set
> > it
> > > at
> > > > > the
> > > > > > > initscript, starting spamd). this gives more debug information
> in
> > > your
> > > > > > > syslog/maillog.
> > > > > > > have you tried 'spamassassin --lint' ? its a syntax check for
> all
> > > .cf
> > > > > > > files. just in case something is broken, the command will
report
> > it.
> > > > > > > and finaly, upgrade to at least 2.63. many changes have been
> done
> > > > since
> > > > > > > 2.44, not to mention those rbl updates.
> > > > > > >
> > > > > > > regards,
> > > > > > > Matthias
> > > > > > >
> > > > >
> > >
>
