You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by John Beranek <jo...@redux.org.uk> on 2004/10/05 13:00:26 UTC
spamc sanity check failures on Suse 9.1
I've just upgraded to SpamAssassin 3.0 and Suse 9.1, and have now
started noticing errors in my mail logs. I'm not sure if it's the OS
upgrade or the SpamAssassin upgrade.
Version info:
$ uname -a
Linux linda 2.6.4-52-default #1 Wed Apr 7 02:08:30 UTC 2004 i686 athlon
i386 GNU/Linux
$ spamassassin --version
SpamAssassin version 3.0.0
running on Perl version 5.8.3
I run spamd with no options, ditto spamc.
The log messages are attached, because of the long lines, I hope the
mailing list doesn't strip attachments.
John.
P.S. A web search turned up problems with previous spamassassin versions
with OSes that use UTF-8 locales by default, and changed spamd and spamc
to run with LANG=C. This seemed to make it fail more often, not less...
--
John Beranek To generalise is to be an idiot.
http://redux.org.uk/ -- William Blake
Re: spamc sanity check failures on Suse 9.1
Posted by John Beranek <jo...@redux.org.uk>.
Michael W Cocke wrote:
[snip]
> you well enough. Off the top, you need to apply your updates - your
> kernel is the original that shipped with 9.1. The sanity check
> message is interesting... how much ram and available disk space have
> you? It would seem the message stream is being chopped somehow
> mid-message. Damned if I can see how that happens, unless you're out
> of storage, or possibly timing out somewhere. More details about your
> configuration please.
I'm not out of storage or memory.
However, I have an update. I changed spamd and spamc options and did a
pretty major CPAN update* (when I realised the new Suse had a different
version of Perl, and therefore a new module tree) and the problem
appears to have gone away.
I've since undone the spamd and spamc options, and the problem hasn't
yet occurred again.
John
* I updated all the required and optional modules for Mail::SpamAssassin
and for Razor. Installed latest version of razor-agents, and reinstalled
Pyzor for a new Python version.
--
John Beranek To generalise is to be an idiot.
http://redux.org.uk/ -- William Blake
Re: spamc sanity check failures on Suse 9.1
Posted by Michael W Cocke <co...@catherders.com>.
On Tue, 05 Oct 2004 19:26:54 +0100, you wrote:
>John Beranek wrote:
>
>>
>> I've not got a spamassassin RPM installed at. I just installed
> ^all
>
>Note to self: Proofread a sentence after rewording it. :)
>
>John.
I'm a past master at the obscure typo late at night, so I understood
you well enough. Off the top, you need to apply your updates - your
kernel is the original that shipped with 9.1. The sanity check
message is interesting... how much ram and available disk space have
you? It would seem the message stream is being chopped somehow
mid-message. Damned if I can see how that happens, unless you're out
of storage, or possibly timing out somewhere. More details about your
configuration please.
Mike-
--
If you can keep your head while those around you are losing theirs...
You may have a great career as a network administrator ahead!
--
Please note - Due to the intense volume of spam, we have installed
site-wide spam filters at catherders.com. If email from you bounces,
try non-HTML, non-encoded, non-attachments,
Re: spamc sanity check failures on Suse 9.1
Posted by John Beranek <jo...@redux.org.uk>.
John Beranek wrote:
>
> I've not got a spamassassin RPM installed at. I just installed
^all
Note to self: Proofread a sentence after rewording it. :)
John.
--
John Beranek To generalise is to be an idiot.
http://redux.org.uk/ -- William Blake
Re: spamc sanity check failures on Suse 9.1
Posted by John Beranek <jo...@redux.org.uk>.
Michael W Cocke wrote:
> On Tue, 05 Oct 2004 12:00:26 +0100, you wrote:
>
>
>>I've just upgraded to SpamAssassin 3.0 and Suse 9.1, and have now
>>started noticing errors in my mail logs. I'm not sure if it's the OS
>>upgrade or the SpamAssassin upgrade.
>
>
> You've probably already checked this, but for the record - the
> /etc/sysconfig/spamd that ships with suse is VERY wrong for SA 3.0.
> Did you fix the command line parms?
I've not got a spamassassin RPM installed at. I just installed
Mail::SpamAssassin from CPAN, and added a /etc/init.d/spamd I found
somewhere on the net...
John.
--
John Beranek To generalise is to be an idiot.
http://redux.org.uk/ -- William Blake
Re: spamc sanity check failures on Suse 9.1
Posted by Michael W Cocke <co...@catherders.com>.
On Tue, 05 Oct 2004 12:00:26 +0100, you wrote:
>I've just upgraded to SpamAssassin 3.0 and Suse 9.1, and have now
>started noticing errors in my mail logs. I'm not sure if it's the OS
>upgrade or the SpamAssassin upgrade.
You've probably already checked this, but for the record - the
/etc/sysconfig/spamd that ships with suse is VERY wrong for SA 3.0.
Did you fix the command line parms?
Mike-
--
If you can keep your head while those around you are losing theirs...
You may have a great career as a network administrator ahead!
--
Please note - Due to the intense volume of spam, we have installed
site-wide spam filters at catherders.com. If email from you bounces,
try non-HTML, non-encoded, non-attachments,