Imho You need 100 ham and 100 spam to auto learning working. Do manual
learning
08.08.2017 8:20 PM "Scott Techlist" napisał(a):
> Centos7
> Postfix 3.2.2
> Amavisd-new 2.11.0
> Spamassassin 3.4.0
> Site-wide configuration
>
> This is a new box and I've configured some conservative values for
> a
On 2015-10-14 18:31, Mark Martinec wrote:
Check your database:
$ spamassassin --lint -D metadata' 2>&1 | fgrep RelayCountry
should yield something like:
Oct 15 01:26:45.584 [78315] dbg: metadata: RelayCountry:
Using database: Geo::IP GEO-106FREE 20151006 Build 1
Copyright (c) 2015 MaxMi
/geoip-api-perl/pull/22
If you click 'Files changed' you'll see the path, and see the fix.
On 10/14/15 11:49 AM, a...@satester.com wrote:
Hi,
We activated the relay country plugin yesterday. As part of the
process
we did a yum install perl-Geo-IP. Now we get the following warning
://github.com/maxmind/geoip-api-perl/pull/22
If you click 'Files changed' you'll see the path, and see the fix.
On 10/14/15 11:49 AM, a...@satester.com wrote:
Hi,
We activated the relay country plugin yesterday. As part of the
process
we did a yum install perl-Geo-IP. Now we get the fo
5520 is in, and I am not finding much in
Google and I'm hoping someone here has a clue. Thanks.
Allen
a...@satester.com
I have been working on satester.com this past week in my spare time and
I put up a new version recently (v1.02). I think I may have finally
nailed it down to where it is usable with a large ruleset. (It threw
errors with pastes of large .cf files and other stuff) I also show the
rule name now
On 2015-07-18 04:54, Martin Gregorie wrote:
There are lots of possibilities. I test using a big (and growing) spam
collection, which I keep so I can regression test my current rule set.
Thats quite crude: if everything in the collection is recognised as
spam, nothing gets flagged up during the t
On 2015-07-17 16:49, Kevin A. McGrail wrote:
We use maildir most of the time on our servers. Is that a problem or
are you referring to a mbox file on a client machine? I never ran
spamassassin on a client before. Sorry, just trying to understand your
test environment.
I usually am working
ers. I try and automate my
stuff as much as possible and these days I can pickup spam patterns in
my sleep...
LOL. I may not be so good at coding patterns, but I can smell a good
spam phrase in a heartbeat. I am also very careful to double check, lint
rules, etc. and I can't be too caref
r methods
of checking/debugging.
Allen
am -at- satester.com
ted by the new tool and I can't wait to dig into mutt and
spamassassin -t today to see how they work by comparison. Yea, no more
Rubular. heh.
Allen Marsalis
am -at- satester.com
t I'll
have to look deeper to understand why you would trigger on any From
address. Anyway I'm having fun, learning a lot, and doing my customers
a lot of good by developing rules. Thanks again for your tips and help.
Allen Marsalis
am -at- satest.com
I started writing SA rules about a year ago. Although I am new to this
list, I have been lurking for quite a while. I would like to thank Kevin
McGrail and others for providing rules and tips that inspires me to
write my own custom rules.
Today I wrote a little tool that helps me test my SA
13 matches
Mail list logo
