Re: TXREP gone wild?

Benjamin Block <[email protected]> Mon, 18 May 2026 18:23:14 +0200
Newsgroups gmane.mail.spam.spamassassin.general
Message-ID <[email protected]>
--NNiiEVd5V7BRwn/I
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Mar 02, 2026 at 09:43:56AM +0100, [email protected] wrote:
> On 3/1/26 3:29 PM, Alex wrote:
> > On Sat, Feb 28, 2026 at 4:20=E2=80=AFPM <[email protected] <mailto:gio=
[email protected]>> wrote:
> >     On 2/27/26 10:11 PM, Alex wrote:
> >      > Hi, are there any known issues with TXREP with the latest spamas=
sassin?
> >      >
> >      > # spamassassin --version
> >      > SpamAssassin version 4.0.3-r1928101
> >      >=C2=A0 =C2=A0 running on Perl version 5.40.3
> >      >
> >      >=C2=A0 =C2=A0* 2867 TXREP TXREP: Score normalizing based on sende=
r's reputation
> >      >
> >      > This is on fedora42. I've now downgraded and the problem seems t=
o be resolved.
> >      >
> >     Do you have downgraded to which version ?
> >=20
> > # spamassassin --version
> > SpamAssassin version 4.0.1
> >  =C2=A0 running on Perl version 5.40.3
>
> there has been a lot of changes between 4.0.1 and 4.0.2 on TxREP
> plugin, have you followed upgrade instructions
> (https://github.com/apache/spamassassin/blob/trunk/UPGRADE) for 4.0.2
> version ?
> In some cases, it's better to truncate sql tables in order to retrain
> TxREP quickly.

Can confirm. I had similar problems with txrep on Fedora recently, and
after finding this post I pruned my whole bayes/txrep SQL database;
after re-learning classification seems to work better again.

I guess bayes would not have been necessary, but whatever. For my
usecase it didn't matter as I'm the only user of the server.

Bit of a shame the system can't handle this "transparently" when calling
`sa-lern` for example. It already handles expire.

--=20
Best Regards und Beste Gr=C3=BC=C3=9Fe, Benjamin Block
               PGP KeyID: 9610 2BB8 2E17 6F65 2362  6DF2 46E0 4E05 67A3 2E9E

--NNiiEVd5V7BRwn/I
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iQGzBAABCAAdFiEElhAruC4Xb2UjYm3yRuBOBWejLp4FAmoLPOoACgkQRuBOBWej
Lp6i4gv/dGoN+q/ioc7/NbVzhLHVWBv6V9xrWWUHnt+KPmivdXwYtWETlxWx4QdD
bFwW1C+O1kA8Vqdm5jVStHPSGLGrpklXkCWZSjluAW9dswkgmn+BML+CQE97p9I1
bL8l7HzqMDgHt+icWpilPMavAKN6kl/Vdpyy0hXhfiBLGToipPscUwKEfUMRHac+
5WakkCxiWqMtE73aDAkoqKfra/ZDGPMHoxcCf/9IwyZWP5l1k+ZgDzep6RZw+XAN
7q9lf3gfhXNxEKjHCUB1j/urlenG7JhrAcjLABkIOZInnY9RRjP1oC+fp6Fe19kw
DkTuW59hq9Z9eZ8jxapPkVrE7bbFliZrodOeh7ZepAH59i75lomRhcfWiNdaHzHq
bi6ZQUPfMbpypcisoDqu00Xn1ASSZMa0ulh4MjSAvjqOKCPuUDKjN7NHPncFDn53
8gjXxfCTCxr2PAk0fki65BRz+k8o2AZI54D8p3b4APFgdH/ejOULxnSMkmtb7kr9
wG9soIIK
=8/tM
-----END PGP SIGNATURE-----

--NNiiEVd5V7BRwn/I--