You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Alex <my...@gmail.com> on 2026/03/01 14:29:38 UTC
Re: TXREP gone wild?
On Sat, Feb 28, 2026 at 4:20 PM <gi...@paclan.it> wrote:
> On 2/27/26 10:11 PM, Alex wrote:
> > Hi, are there any known issues with TXREP with the latest spamassassin?
> >
> > # spamassassin --version
> > SpamAssassin version 4.0.3-r1928101
> > running on Perl version 5.40.3
> >
> > * 2867 TXREP TXREP: Score normalizing based on sender's reputation
> >
> > This is on fedora42. I've now downgraded and the problem seems to be
> resolved.
> >
> Do you have downgraded to which version ?
>
# spamassassin --version
SpamAssassin version 4.0.1
running on Perl version 5.40.3
# rpm -q spamassassin
spamassassin-4.0.1-6.fc42.x86_64
> Thanks
> Giovanni
>
Re: TXREP gone wild?
Posted by Benjamin Block <be...@mageta.org>.
On Mon, Mar 02, 2026 at 09:43:56AM +0100, giovanni@paclan.it wrote:
> On 3/1/26 3:29 PM, Alex wrote:
> > On Sat, Feb 28, 2026 at 4:20 PM <giovanni@paclan.it <ma...@paclan.it>> wrote:
> > On 2/27/26 10:11 PM, Alex wrote:
> > > Hi, are there any known issues with TXREP with the latest spamassassin?
> > >
> > > # spamassassin --version
> > > SpamAssassin version 4.0.3-r1928101
> > > running on Perl version 5.40.3
> > >
> > > * 2867 TXREP TXREP: Score normalizing based on sender's reputation
> > >
> > > This is on fedora42. I've now downgraded and the problem seems to be resolved.
> > >
> > Do you have downgraded to which version ?
> >
> > # spamassassin --version
> > SpamAssassin version 4.0.1
> > 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.
--
Best Regards und Beste Grüße, Benjamin Block
PGP KeyID: 9610 2BB8 2E17 6F65 2362 6DF2 46E0 4E05 67A3 2E9E
Re: TXREP gone wild?
Posted by gi...@paclan.it.
On 3/1/26 3:29 PM, Alex wrote:
>
>
> On Sat, Feb 28, 2026 at 4:20 PM <giovanni@paclan.it <ma...@paclan.it>> wrote:
>
> On 2/27/26 10:11 PM, Alex wrote:
> > Hi, are there any known issues with TXREP with the latest spamassassin?
> >
> > # spamassassin --version
> > SpamAssassin version 4.0.3-r1928101
> > running on Perl version 5.40.3
> >
> > * 2867 TXREP TXREP: Score normalizing based on sender's reputation
> >
> > This is on fedora42. I've now downgraded and the problem seems to be resolved.
> >
> Do you have downgraded to which version ?
>
>
> # spamassassin --version
> SpamAssassin version 4.0.1
> 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.
Giovanni