Re: Delays with Check_Bayes

On Thu, 2014-08-21 at 13:13 -0700, redtailjason 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 have been developing and upgrade plan to 3.4. Based on this, we are > prioritize this upgrade and will be

Re: Delays with Check_Bayes

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

Re: Delays with Check_Bayes

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 offering an a

Re: Delays with Check_Bayes

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 st

Re: Delays with Check_Bayes

On Wed, 2014-08-20 at 13:38 -0700, 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. Please let > me know if this does not fully clarify our setup for you. So we're talking about 1% of

Re: Delays with Check_Bayes

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 offering an alt

Re: Delays with Check_Bayes

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

Re: Delays with Check_Bayes

On Wed, 2014-08-20 at 06:15 -0700, redtailjason wrote: > 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 anyo

Re: Delays with Check_Bayes

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:

Re: Delays with Check_Bayes

On Wed, 2014-08-20 at 08:51 -0700, redtailjason wrote: > 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. It doesn't matter what user greps the logs. It was Amavis generating the logs. Thus, for debug

Re: Delays with Check_Bayes

On Wed, 2014-08-20 at 07:35 -0700, redtailjason wrote: > 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 version > 0.000 0613 0 non-token

Re: Delays with Check_Bayes

On 20. aug. 2014 17.36.39 redtailjason wrote: $ 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 rfc 1700 is already in default sa config, tanks for that to developpers :) May miss rfc 1918 defined in lokal.cf,

Re: Delays with Check_Bayes

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

Re: Delays with Check_Bayes

On 08/20/2014 05:35 PM, redtailjason wrote: 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::Pl

Re: Delays with Check_Bayes

Do not have enough HAM to kick on bayes. -- Jeremy McSpadden Flux Labs | http://www.fluxlabs.net | Endless Solutions Office : 850-250-5590x501 | Cell : 850-890-2543 | Fax : 850-254-2955 On Aug 20, 2014, at 10:36 AM, "redtailjason" mailto:ja...@redtailtechnology.com>>

Re: Delays with Check_Bayes

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

Re: Delays with Check_Bayes

On Wed, 20 Aug 2014, redtailjason wrote: Thank you for your response! Our Bayes is MySQL. Currently, the expiry runs via cron job to run during low volume times. Does the MySQL log say anything suggestive? Here is the dump from one of the scanners: netset: cannot include 127.0.0.1/32 as it

Re: Delays with Check_Bayes

On 08/20/2014 04:35 PM, redtailjason wrote: 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

Re: Delays with Check_Bayes

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

Re: Delays with Check_Bayes

On 08/20/2014 03:15 PM, redtailjason wrote: 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

Delays with Check_Bayes

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