Hi all.
I am running SA version 3.4.1 on Debian Jessie (from the backport archives). SA
run through Amavis and so far I did not have any problem, nor with the
classification orthe updates through sa-update. Following the advises on the SA
wiki (https://wiki.apache.org/spamassassin/ImproveAccurac
Hi.
Why do you think bayes have problems with such email?
Considering the example you put on Pastebin is triggering
"BAYES_00=-1.9" I believe that if you are able to collect
a sufficient amount of these messages and feed it to SA
through sa-learn you should start to trigger more BAYES_5X
or even
Thanks a lot for the explanation Mark, it was very clear.
It would be a good idea considering to add that to the
perldoc of the BayesStore/Redis.pm module.
Regards,
Matteo
On 27.02.2015 14:55, Mark Martinec wrote:
When redis automatically expires tokens internally based on their
TTL, this o
On 27.02.2015 13:54, Axb wrote:
Is it possible you reject so much spam tha SA sees very little spam?
I believe it's the case. A combination of Postfix policies, blacklists,
ClamAV plus additional signatures, etc. greatly reduces the amount of
email sent through the filtering pipeline.
If cl
Hi all.
I am using a centralized Redis instance to
host the bayesian data for a bunch of MTAs.
AFAICS the SA filter is working quite well
and the BAYES_* rules are triggered correctly,
no false positive so far.
But I am concerned about the expiration of the
bayesian data. sa-learn reports the f
Hello.
Sorry Axb, I don't want to be pedant but the latest
'svn export' you have suggested gave me an error:
"svn: Repository moved permanently to (other location)".
Indeed, if I try:
svn export
http://svn.apache.org/repos/asf//spamassassin/trunk/lib/Mail/SpamAssassin/Util/RegistrarBoundaries.
Hello.
I am just curious, since I am using SaneSecurity
signatures too.
According to: http://sanesecurity.com/usage/signatures/
some of the lists you mentioned have been classified
with 'medium' to 'high' risk of false positives:
foxhole_*
spear / spearl
Did you not get into trouble with those
Uh,ohsorry my bad. I did it try the modifed ruleset on
a test installation without the Rule2XSBody plugin enabled.
With the plugin enabled (and after restarting Amavis) it looks
like those warning messages are not there anymore.
Thanks a lot for the fix!
Regards,
Matteo
On 10.02.2015 16:
Hello KAM.
Unfortuntately I am still getting the same "warning messages"
with the new 25_spf.cf.
It looks like that the check part:
if can(Mail::SpamAssassin::Plugin::SPF::has_check_for_spf_errors)
(...)
endif
is ignored. Could it be an effect introduced by the sa-compile step?
The output of t
Hi all.
I am getting the same errors. I am running SA through Amavis but I guess
it does not matter in this case. Is there a way of fixing those errors,
apart from disabling the rules from 25_spf.cf?
SA version: 3.4.0 - Perl 5.14.2 (Debian Wheezy - 64 bit)
Log snapshot:
Feb 9 10:
Hi.
@Mark: thanks for the explanations about Amavis/SA.
@Reindl: thanks, I am indeed using unbound as a DNS
caching server. Interesting the option 'minimal-responses',
I would check that.
Regards,
Matteo
On 02.12.2014 14:16, Mark Martinec wrote:
Matteo Dessalvi wrote:
I ha
Yes, I have read the docs but I was not sure if SA,
when used through Amavis, would use such option.
Nevermind, I pushed up the log verbosity of my DNS
caching service and it looks like SA is using it.
So, problem solved :-).
Thanks.
Best regards,
Matteo
On 02.12.2014 13:18, Axb wrote:
doh..
Hi all.
I have a short question about the dns_server option of SA.
Is this option used when SA is called from Amavis and there
isn't any spamd process running?
To be more clear: should I also be forced to add the IP
address of the caching DNS server to /etc/resolv.conf
or the option would be suf
Since you are mentioning 'Out of office' messages
Is anybody else got in trouble due to this 'fantastic'
auto responder feature? Especially when these email
are generated by an Exchange server.
Just curious, since the last week one of our mail
server (for outbound traffic) got listed in one
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
assin/tags/spamassassin_current_release_3.4.x/sql/README.bayes
Regards,
Matteo
Quoting Matteo Dessalvi :
Hi.
I did test a similar configuration a while ago and had the same problem.
If you take a look at this thread on the mailing list:
http://spamassassin.1065346.n5.nabble.com/Bayes-vars-records-on-MySQL-n
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
Hi.
I did test a similar configuration a while ago and had the same problem.
If you take a look at this thread on the mailing list:
http://spamassassin.1065346.n5.nabble.com/Bayes-vars-records-on-MySQL-not-created-automatically-td104615.html
you'll see it was a problem of running 'sa-learn --sy
Ok, perfect! Thanks a lot! This is what I want to know
and I was not so sure about.
I may be wrong but it looks to me the fact that
tools like sa-learn can access transparently the
backends configured for SA is not exactly clear
from the docs.
It would be great if the wiki maintainers could add
No, unfortunately it does not help me.
I already have a proper config file for SA
to access Redis as backend and most of
the configurations are done automatically
through a Chef cookbook (Redis included).
In the docs you pointed me there's nothing
about the interaction between sa-learn and
Redis.
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 planning
to use Redis as a centralized backend (previously
the bayes db were just files save
Hi all.
Thanks for all the answers. I am afraid I was being naive.
I was explicitly thinking of a scenario like this: filter as
much as possible 'unsolicited email' sent by some (possibly)
'infected' account.
I thought that turning off the bayesian classifier (and the
RBL checks) would still let
Hi all.
This may be a very stupid question but I would like to ask you all
anyway.
I am planning to install SA on our SMTP MTAs, which deals only with
outgoing traffic generated in the internal network.
I am making the assumption that our clients are mostly sending 'clean'
email (I know, I am tr
Yes, you are definitely right: with the latest stable
Redis version (2.8.9 indeed) everything works smoothly
with the authentication.
Thanks for pointing me in the right direction!
Best regards,
Matteo
On 22.05.2014 14:10, Axb wrote:
You're using an ancient Redis version with no LUA support.
On 22.05.2014 13:10, Axb wrote:
have you included this in your local.cf ?
bayes_store_module Mail::SpamAssassin::BayesStore::Redis
These are the relevant configuration lines for the
Redis SA module:
bayes_store_module Mail::SpamAssassin::BayesStore::Redis
bayes_sql_dsn server=10.1.1.1
Hi all.
As stated in the subject I am just trying to test my
SpamAssassin 3.4.0 installation (I am using the Debian
Jessie package), with the usual method described here:
http://wiki.apache.org/spamassassin/TestingInstallation
In the output of the command: spamassassin -D < gTube_spam.txt
I hav
As far as I understand only the 3.4 (devel branch) version of SA is supporting
Redis as a Bayes storage.
Are you using this version in production? Can you tell us, approximately, the
volume of the email traffic?
Are you running a configuration with multiple SA connected to a single Redis
insta
Hi Fabio.
Have you tried also the 'Language options' of SpamAssassin? Like the one
described here:
http://spamassassin.apache.org/full/3.2.x/doc/Mail_SpamAssassin_Conf.html#language_options
Matteo
- Messaggio originale -
Da: Fabio Sangiovanni
A: users@spamassassin.apache.org
Cc:
Invi
___
Da: Michael Parker
A: Matteo Dessalvi
Cc: "users@spamassassin.apache.org"
Inviato: Mercoledì 8 Maggio 2013 18:43
Oggetto: Re: Bayes_vars records on MySQL not created automatically
On May 8, 2013, at 8:06 AM, Matteo Dessalvi wrote:
>
> I always thought that S
Hi all.
I do hope that this question is not outside the scope of the list and
I apologize in advance if that is the case.
Currently I'am running this configuration on an email gateway server:
- Debian Linux Wheezy
- Postfix 2.9.6-2
- Spamassassin 3.3.2
- Amavisd-new 2.7.1
- Perl 5.14.2
- MySQL 5
30 matches
Mail list logo