On Wed, Feb 05, 2020 at 06:21:42PM -0500, Kris Deugau wrote:
> Kevin A. McGrail wrote:
> >You can store the userprefs in an SQL database.
>
> Seconded, for blacklist_*/whitelist_* in particular this works very well.
>
> Locally I've also set this custom query:
>
> user_scores_sql_custom_query
Kevin A. McGrail wrote:
You can store the userprefs in an SQL database.
Seconded, for blacklist_*/whitelist_* in particular this works very well.
Locally I've also set this custom query:
user_scores_sql_custom_query SELECT preference, value FROM
spamassassin_userpref WHERE username =
You can store the userprefs in an SQL database.
On 2/5/2020 11:04 AM, hwi wrote:
> To more specific: at least the whitelist/blacklist configs should be loaded
> dynamically. The more flexibility the better.
> Is there a way to load configs during runtime without using a dnsbl?
--
Kevin A.
On Wed, Feb 05, 2020 at 09:04:29AM -0700, hwi wrote:
> Dear spamassassin dev-heroes,
> spamassassins config is loaded at startup via Mail::SpamAssassin::Conf.
> I wonder if there is a way to load or change certain config items
> dynamically during sa runtime without a restart. I;ve played with
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7794
Bill Cole changed:
What|Removed |Added
Assignee|dev@spamassassin.apache.org |billc...@apache.org
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7794
Bug ID: 7794
Summary: maxhits is not always honored for body rules
Product: Spamassassin
Version: 3.4.4
Hardware: PC
OS: FreeBSD
Status: NEW
Dear spamassassin dev-heroes,
spamassassins config is loaded at startup via Mail::SpamAssassin::Conf.
I wonder if there is a way to load or change certain config items
dynamically during sa runtime without a restart. I;ve played with the
Mail::SpamAssassin::Conf::Parser API in permsgstatus during
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7618
--- Comment #26 from Ondrej Lysonek ---
OK. Thank you!
--
You are receiving this mail because:
You are the assignee for the bug.
HTTP get: https://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: https://ruleqa.spamassassin.org/2-days-ago?xml=1
HTTP get: https://ruleqa.spamassassin.org/3-days-ago?xml=1
Bad performing rules, from the past 3 night's mass-checks.
(Note: 'net' rules will be listed as 'no hits' unless you