[EMAIL PROTECTED](Jamie L. Penman-Smithson) 17.07.05 13:31
>Your rule has a trailing space,
i know that. Without it did not work either.
>since all log messages have trailing
>spaces stripped before they are processed, your rule will never match
>anything.
Sorry, i wasn't aware of that and throught something wiered inside logcheck.
That's why i file a bug.
Too i was not warned that testing rules with "egrep -f"
is not recommandable/is senseless, because logcheck modifies the logfile reads.
>Removing the trailing space should fix the problem:
>^\w{3} [ :0-9]{11} [._[:alnum:]-]+ spamd\[[0-9]+\]: Argument \"RBL\"
>isn't numeric in addition \(\+\)
>at /usr/share/perl5/Mail/SpamAssassin/Conf.pm line 244.$
Yes! I wonder why it did not work some days before...
>Finally, this message indicates a _PROBLEM_ with your spamassassin
>configuration, ignoring it _will not_ make the problem disappear.
I assume it's problem in some users config...
I don't want "littering" logcheck mails with messages i
can't change. That's to dangerous as some day no one will
take a look into the file.
>Ignoring errors is not a good strategy. See bug #3853 in SA's bugzilla
>(which I found within 5 seconds using Google)
I have several(!) times tried google and did not find any useful hints
or solution.
Which words did you use?
I tried "Argument isn't numeric in addition" etc. with spamd and without
and only see that others asking the same.
http://www2.list.logwatch.org:81/pipermail/logwatch/2004-February/000459.html
no access..
http://www.dclug.org.uk/archive/2004/09/msg00214.html
no answer
http://www.mailarchives.org/list/spam-assassin/msg/2004/11717
no answer
etc.
The error is very common.
>which was the result of misconfiguration:
>> ------- Additional Comments From [EMAIL PROTECTED] 2004-10-01
>> 10:05 -------
>> This type of issue has always been something like:
>>
>> score FOO_RULE RBL 3
>>
>> somewhere in the configuration files. Could be in any of
>> the /etc/mail/spamassassin/*.cf files, or in
>> user_prefs, or anywhere your SA installation gets configuration data
>> from.
>Fix the problem in your SA configuration.
"find the user with the wrong config!" ;-)
Rainer
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
