https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7943
--- Comment #3 from Matija Nalis <mnalis-sa...@voyager.hr> --- Thanks Paul for your efforts! Unfortunately, I hadn't had a change to try your fix yet, as I've had to drop TxRep in favor of AWL in early 2022 in order to make production functional again, and not having time to try to test and bring it back... However, since AWL with SQL backend also seems buggy, and I'll have to invest time to rebuild database anyway, I think I might give TxRep another try. Might be worth doing it before 4.0 gets out, in order to iron out bugs there and save other people some headaches. However, I've found another bug in SQLBasedAddrList.pm which seems it might be affecting not only AWL but TxRep as well: https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8072 Could you take a look there if that would affect TxRep as well? Also, can I just grab SQLBasedAddrList.pm and TxRep.pm from trunk; or do I have to go full-trunk (which would be much harder to swallow as I can basically test it only by deploying it in production) ? -- You are receiving this mail because: You are the assignee for the bug.
