Hello. We are seeing an issue where spoofed spam is being whitelisted to our
domain. We host over 10,000 mailboxes but the issue is only occurring to
within our corporate domain. I have checked all local configs on our eight
scanners and do not show that our domain has been whitelisted.
Our prima
Hello. We are seeing an issue where spoofed spam is being whitelisted to our
domain. We host over 10,000 mailboxes but the issue is only occurring to
within our corporate domain. I have checked all local configs on our eight
scanners and do not show that our domain has been whitelisted.
Our prima
Hello. We are seeing an issue where spoofed spam is being whitelisted to our
domain. We host over 10,000 mailboxes but the issue is only occurring to
within our corporate domain. I have checked all local configs on our eight
scanners and do not show that our domain has been whitelisted.
Our prima
On 21/08/14 09:00, John Hardin wrote:
>
> Are you open to the possibility of upgrading to 3.4.0 and using the
> Redis backend for Bayes? (Just offering an alternative.)
>
We just last week moved over to 3.4.0 with a central Redis backend with
6 spamd servers spread over USA and Europe. Bit of a s
On Wed, 20 Aug 2014, redtailjason wrote:
> We are seeing about 4000-7000 delayed messages per day. We do utilize a
> dedicated MySQL Server for the Bayes and all 8 scanners share it.
Are you open to the possibility of upgrading to 3.4.0 and using the Redis
backend for Bayes? (Just offer
We are seeing about 4000-7000 delayed messages per day. We do utilize a
dedicated MySQL Server for the Bayes and all 8 scanners share it. Please let
me know if this does not fully clarify our setup for you.
Has anyone heard of a configuration where the transactions are written to a
file (ie text
Thank you for the clarification, sorry about that. Below is the updated
information:
sa-learn --dump magic
0.000 0 3 0 non-token data: bayes db version
0.000 02687726 0 non-token data: nspam
0.000 0 846578 0 non-token data:
AXB,
The initial post was data extracted from mail.log on the scanner using cat
/var/log/mail.log | grep check_bayes while logged as administrator.
--
View this message in context:
http://spamassassin.1065346.n5.nabble.com/Delays-with-Check-Bayes-tp111067p111081.html
Sent from the SpamAssass
Below is the output that you are seeking:
$ spamassassin --lint -D bayes
Aug 20 07:54:53.816 [6955] warn: netset: cannot include 127.0.0.1/32 as it
has already been included
Aug 20 07:54:54.415 [6955] dbg: bayes: learner_new
self=Mail::SpamAssassin::Plugin::Bayes=HASH(0x382ddd0),
bayes_store_modu
Thank you for your response! Our Bayes is MySQL. Currently, the expiry runs
via cron job to run during low volume times.
Here is the dump from one of the scanners:
netset: cannot include 127.0.0.1/32 as it has already been included
0.000 0 3 0 non-token data: bayes db
Hello and good morning. We are running into some delays that we are trying to
pin down a root cause for.
Below are some examples. Within the examples, you can see that the
check_bayes: scan is consuming most of the timing. Does anyone have any
suggests on what to look at? We use 3.3.2. We have ei
11 matches
Mail list logo
