Tobi, can you open a bug about this and add a spample of the issue? ch is
in the TLD list 20_aux_tlds.cf.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Mon, Nov 9, 2020 at 9:56 AM Tobi wro
Those can be ignored. They are by design.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Thu, Nov 19, 2020 at 9:26 AM Dean Carpenter <
deano-spamassas...@areyes.com> wrote:
> On 2020-11-18
TxRep could have some bugs but I've not found it to cause a FP in years
so it's generally safe for production use. Do you have an email that might
replicate the issue?
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcg
Hi Dan,
Milters are the glue that change the email. SpamAssassin is just giving
data back to the milter.
I believe you will find that X-Spam-Status header is being built by
spamass-milter not by spamassasin. You need to change the milter code to
keep track of the user and add it to the X-Spam-S
On 2021-03-13 21:08, RW wrote:
On Sat, 13 Mar 2021 09:22:53 -0800 (PST)
John Hardin wrote:
I'm not sure offhand if BAYES_50 hits when bayes is enabled but
insufficiently trained...
It doesn't.
it could be added so when its not trained show its needs more data
meta BAYES_NOT_TRAINED (!BAYE
- Message from a...@onet.eu -
Date: Fri, 12 Mar 2021 13:16:25 +0100
From: a...@onet.eu
Subject: sa-update error 3 no mirrors.sought.rules.yerp.org
To: users@spamassassin.apache.org
Hi,
I'm getting this from cron since two days:
channel: no 'mirrors.sought.rules.yerp.org'
On Sat, 13 Mar 2021 09:22:53 -0800 (PST)
John Hardin wrote:
> I'm not sure offhand if BAYES_50 hits when bayes is enabled but
> insufficiently trained...
It doesn't.
Are there any BAYES hits on their messages, ham or spam? BAYES_{not
50} would be a positive confirmation. I'm not sure offhand if BAYES_50
hits when bayes is enabled but insufficiently trained...
In one email, I'm seeing this:
3.0 BAYES_95 BODY: Bayes spam probability is 95 to
On Sat, 13 Mar 2021, Steve Dondley wrote:
I *think* I now I have site-wide bayes filtering working now for all users on
a server. I've edited /etc/spamassassin/local.cf to include "bayes_path" and
"bayes_file_mode" and I don't see any errors about permissions being wrong
from debian-spamd in m
I *think* I now I have site-wide bayes filtering working now for all
users on a server. I've edited /etc/spamassassin/local.cf to include
"bayes_path" and "bayes_file_mode" and I don't see any errors about
permissions being wrong from debian-spamd in mail.log.
But rather than guessing, I'm won
10 matches
Mail list logo