-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
C'mon people, post messages...ANY messages. I need input for my filters and
spamassassin testing.
There appears to be a bit of a problem with kmail and filters if you upgrade
spamassassin. I started out with the 9.1-supplied spamassassin-2.44, which
was working fine both in client mode and in daemon mode from kmail (KDE
3.1.0). Then I upgraded to spamassassin-2.54 from cooker (along with its
dependencies) and though the logs indicated spamassassin was working OK, my
kmail filter for piping through spamc no longer worked. I then went back to
spamassassin-2.44 but the problem remained. I deleted my spamassassin filter
and reentered it identical to before. Now spamassassin was working again.
I upgraded once again to 2.54 and poof, it quit working again. I deleted my
spamassassin filter and reentered it identical to before and now it seems to
be working again. What the fuh? Can anyone else duplicate this?
The dependencies for 2.54 include upgrading to perl-5.8.0-22mdk from
5.8.0-19mdk but no big whup.
praedor
On Thursday 29 May 2003 12:59 pm, Praedor Atrebates wrote:
> On Thursday 29 May 2003 12:19 pm, Praedor Atrebates wrote:
> > I just upgraded my spamassassin from the 9.1 version (2.44) to that in
> > Cooker (2.54). I then restarted spamassassin in daemon mode
> > ("/etc/init.d/spamassassin restart") and it started right up. It doesn't
> > appear to work any longer however. Incoming emails no longer get the
> > X-Spam-Status header nor any other header addition that indicates that
> > spamassassin has processed the email.
> >
> > My filter hasn't changed, that is, I pipe all email through spamc -s
> > 600k. This was working fine with 2.44 but not with 2.54?
>
> Well, now I am definitely unhappy with spamassassin. It is not functional.
> I upgraded from the 9.1 spamassassin (version 2.44) to the cooker version
> (2.54). All went well, no errors, no complaints. After the upgrade, I
> stopped and restarted spamd and it started just fine. My filter for
> spamassassin in kmail is thus:
>
> Match all of the following
> <any header> contains .
> pipe through spamc -s 600k
>
> This filter worked fine before I tried the spamassassin upgrade - all my
> mail was analyzed and headers added from spamassassin. Since the upgrade,
> nothing at all happens with spamassassin even though it is running. It is
> the first filter in my list of filters.
>
> I then removed spamassassin-2.54 and went back to 2.44 and it still is DOA.
> What's the deal here? It is running and my filter has remained unchanged,
> but spamassassin isn't doing anything.
>
> praedor
- --
I'm jealous of the Iraqis. I wish someone would "liberate" the United States
of America from its unelected dictator
- --Marc Perkel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+1lczaKr9sJYeTxgRAmQNAJsHvLA2fi/Fz/h1G7oeGff0DXEd/QCfRggq
AkaIP6eVTtsbDyJjFOZtg/Q=
=hx6V
-----END PGP SIGNATURE-----
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
