Thanks for pointing me into the right direction. That helped me solve
the issue.
In fact there was no issue. I just had to run sa-learn -u user
--spam miss-classified-message.txt.
This command added some content into the Bayes tables and the warning
in the debug output was gone.
So that
On Wed, 20 Aug 2014, Nicolás wrote:
Ok, already done that, waited a few hours and now the 'correct'
DNS host appears in the header, but is still marked as spam.
On 20.08.14 20:14, Nicolás wrote:
This would be the latest test:
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
El 21/08/2014 11:07, Matus UHLAR - fantomas escribió:
On Wed, 20 Aug 2014, Nicolás wrote:
Ok, already done that, waited a few hours and now the 'correct' DNS
host appears in the header, but is still marked as spam.
On 20.08.14 20:14, Nicolás wrote:
This would be the latest test:
Although this mail doesn't seem to be spam, it is always marked as
it would be by Google. I just don't understand what makes Google think
it is!
If it is marked by Google, it has nothing to do with your SA.
IMHO, Google is not making such a good job as marking spam, I get way to
many FP (many
On 08/21/2014 12:11 PM, Nicolás wrote:
El 21/08/2014 11:07, Matus UHLAR - fantomas escribió:
On Wed, 20 Aug 2014, Nicolás wrote:
Ok, already done that, waited a few hours and now the 'correct' DNS
host appears in the header, but is still marked as spam.
On 20.08.14 20:14, Nicolás wrote:
El 21/08/2014 11:16, Olivier Nicole escribió:
Although this mail doesn't seem to be spam, it is always marked as
it would be by Google. I just don't understand what makes Google think
it is!
If it is marked by Google, it has nothing to do with your SA.
I know, I was just answering the
On 08/21/2014 12:16 PM, Olivier Nicole wrote:
Although this mail doesn't seem to be spam, it is always marked as
it would be by Google. I just don't understand what makes Google think
it is!
If it is marked by Google, it has nothing to do with your SA.
IMHO, Google is not making such a good
El 21/08/2014 11:26, Axb escribió:
On 08/21/2014 12:16 PM, Olivier Nicole wrote:
Although this mail doesn't seem to be spam, it is always marked as
it would be by Google. I just don't understand what makes Google think
it is!
If it is marked by Google, it has nothing to do with your SA.
W dniu 20.08.2014 o 14:42, Axb pisze:
On 08/20/2014 02:25 PM, Matteo Dessalvi wrote:
Hi all.
I am managing a bunch of Linux MTAs which are placed in
front of some Exchange servers. In such a configuration
the Bayes filter is deployed site-wide.
For a new deployment of these servers I am
I am pretty sure SA support the Redis authentication mechanism.
For my tests I have used the following line:
bayes_sql_dsn server=127.0.0.1:6379;password=MySecretPWD;database=2
Matteo
On 21.08.2014 12:56, Marcin Mirosław wrote:
Hi!
I'm reading bayes_redis.cf and I can see:
#NOTE: We're not
On 21.08.2014 09:20, Michael wrote:
So that means, that actually I do not have to do any action on newly
created users. Once they retrain their first message, the Bayes entries
are getting created. Before that, Bayes is not used for that user. Is
that correct?
Yes, I would say it correct. To
W dniu 21.08.2014 o 13:45, Matteo Dessalvi pisze:
I am pretty sure SA support the Redis authentication mechanism.
For my tests I have used the following line:
bayes_sql_dsn server=127.0.0.1:6379;password=MySecretPWD;database=2
Thanks Matteo,
firstly I should try then write to ML:) So now I
Which version of Redis are you using? I did have some
problems with the 2.4 version packaged by Debian and
I did solve a similar problem using a more recent
version, like the 2.7 or 2.8.
Matteo
On 21.08.2014 14:45, Marcin Mirosław wrote:
W dniu 21.08.2014 o 13:45, Matteo Dessalvi pisze:
I am
FYI that the SA VM machine was added to the list and will be down
shortly today.
regards,
KAM
Forwarded Message
Subject:[NOTICE] - Planned outage for VMWare Host. Affects Multiple VMs
Date: Thu, 21 Aug 2014 10:51:35 +0100
From: Gavin McDonald
W dniu 21.08.2014 o 15:20, Matteo Dessalvi pisze:
Which version of Redis are you using? I did have some
problems with the 2.4 version packaged by Debian and
I did solve a similar problem using a more recent
version, like the 2.7 or 2.8.
And you fixed my problem! Indeed, upgrading from
How's this coming? I'm still showing July 28 as the last update. (Not
complaining - I appreciate all you guys do!)
...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4500
Registered Linux User
On 08/21/2014 09:25 PM, Kevin Miller wrote:
How's this coming? I'm still showing July 28 as the last update.
(Not complaining - I appreciate all you guys do!)
unless there's a new wave of starved masscheckers update should be
published this weekend.
Of couse, the project could always use
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
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
On Thu, 21 Aug 2014, Kevin Miller wrote:
How's this coming? I'm still showing July 28 as the last update. (Not
complaining - I appreciate all you guys do!)
From the latest run:
On 8/20/2014 10:25 PM, UpdatesD Cron wrote:
Exit Status 9 is not zero for do-nightly-rescore-example.
HAM:
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
21 matches
Mail list logo
