Thanks for the reply.
I will try to register it in bugzilla little by little.
2024-06-03 17:04 に giova...@paclan.it さんは書きました:
On 6/3/24 1:10 AM, Tomohiro Hosaka wrote:
Slight correction.
2024-06-03 07:55 に Tomohiro Hosaka さんは書きました:
Here $rc is dualvar.
https://metacpan.org/pod/DBI#execute
Slight correction.
2024-06-03 07:55 に Tomohiro Hosaka さんは書きました:
Here $rc is dualvar.
https://metacpan.org/pod/DBI#execute
This is not dualvar, exactly.
However, the patch is unchanged.
Evaluated as a bool, it is "0E0" true; evaluated as a number, it is the
number of cases.
You ma
Hello.
EMAIL_IP is not evaluated with SQLBasedAddrList.
In conclusion, the following patches are needed.
---
../Mail-SpamAssassin-4.0.1.orig/lib/Mail/SpamAssassin/SQLBasedAddrList.pm 2024-03-26
13:52:11.0 +0900
+++
../Mail-SpamAssassin-4.0.1/lib/Mail/SpamAssassin/SQLBasedAddrList.pm
Hello.
I am using TxRep with DBBasedAddrList.
If we learn the following email
ham is email address user@host with signed
spam is email address without user@host without signed
The following reputation is used
ham is [EMAILIP: user@host, rep:xx, count: xx]
spam is [EMAIL: user@host, rep: xx, co
Hello.
In conclusion, the following patch is needed.
---
../Mail-SpamAssassin-4.0.1.orig/lib/Mail/SpamAssassin/Plugin/TxRep.pm
2024-03-26 13:52:09.0 +0900
+++ ../Mail-SpamAssassin-4.0.1/lib/Mail/SpamAssassin/Plugin/TxRep.pm
2024-06-01 05:09:01.496565000 +0900
@@ -1967,10 +1
->count() > 0 && defined $self->{txrep_dilution_factor}) {
+die; # It will never be processed here.
my $diluted_total =
($self->count() + 1) *
($self->{txrep_dilution_factor} * $self->total() + $score) /
Thanks.
2024-05-30 21:38 に Bill Cole さんは書きました:
Hello.
The code seems to be wrong.
Thanks.
Mail-SpamAssassin-4.0.1
--- lib/Mail/SpamAssassin/Plugin/TxRep.pm.orig 2024-03-26
13:52:09.0 +0900
+++ lib/Mail/SpamAssassin/Plugin/TxRep.pm 2024-05-30
16:50:22.708673000 +0900
@@ -1668,11 +1668,11 @@
$self->{entry}->{msgcount}
Hello.
I have a question about Mail::SpamAssassin::BayesStore::DBM (DB_File).
I am using it with Mail::SpamAssassin::Locker::Flock.
I think this module is implemented as follows
For reading, tie_db_readonly tie (no lock)
For writing, tie_db_writable flock LOCK_EX & tie
multi-process $sa->check