First off, WOW. Our rebuild times are in no way similar. At first I
thought it was you with fancy SSD's and lots of horsepower, but I'm seeing
now that you have both useDB4Rebuild off and RebuildUseFileModel on. The
opposite of my settings. I have useDB4Rebuild on and never enabled the
Nov-12-21 04:00:20 RebuildSpamDB-thread rebuildspamdb-version 8.14 started
in ASSP version 2.6.6(21314)
Nov-12-21 04:00:20 detection of local disclaimers is enabled
Nov-12-21 04:00:20 info: 'useDB4Rebuild' is NOT set to on - the rebuild
spamdb process will possibly require a large amount of
worker_1 is blocked because the AUTH check comes first and AUTH was used
worker_2 is blocked by PenaltyDelay - AUTH was not used
both are blocked before the PenaltyExtreme check is done
Thomas
Von:"Dirk Kulmsee"
An:
Datum: 12.11.2021 14:47
Betreff:[Assp-test]
Absolutely I've thought about this. I consider everything I post prior to
posting.
Can you briefly explain why the ability to scan (MaxBytes + some additional
amount)kb on incoming mails for bombs but only use MaxBytes for bayesian
and the rebuild would be such a bad idea?
Since you questioned
Hi all,
I'm currently running ASSP 2.6.6. (21306) on Linux with Perl 5.32.
I have set both DoPenaltyExtreme and DoPenaltyExtremeSMTP to "block". My
ExtremePenaltyTheshold (PenaltyExtreme) is set to 1500.
In the log I see a candidate for extreme treatment, but the log lines do not
mention the
