>I'm running SA 3.4 and am getting several messages like both of these,
headers below, that are getting through. I've run sa-learn on my Spam folder
to train Sa, but still they're getting through. There are two separate sets
of full headers x-d out to avoid giving server information, but revealing
On 01/21/2015 11:47 PM, David Mehler wrote:
> Hello,
>
> I'm running SA 3.4 and am getting several messages like both of these,
> headers below, that are getting through. I've run sa-learn on my Spam
> folder to train Sa, but still they're getting through. There are two
> separate sets of full hea
Hello,
I'm running SA 3.4 and am getting several messages like both of these,
headers below, that are getting through. I've run sa-learn on my Spam
folder to train Sa, but still they're getting through. There are two
separate sets of full headers x-d out to avoid giving server
information, but rev
mls wrote:
The Rule2XSBody plugin is loaded on ubuntu in sa-compile.pre.
After commenting it out the issue no longer happened.
Great, that is an important finding!
Benny Pedersen wrote:
warn dont use cpan direct in ubuntu, you will break dependice, and
later ask why does it not work
if you
On 21. jan. 2015 22.58.32 mls wrote:
On Tuesday 20 January 2015 20:17:57 Mark Martinec wrote:
> It may be worth trying with the current trunk version from SVN
> (a would-be-3.4.1), as Kevin suggested, so that we'd be on the same
> page.
>
>
> http://wiki.apache.org/spamassassin/DevelopmentStuff
On 21. jan. 2015 22.57.37 mls wrote:
On Tuesday 20 January 2015 18:30:18 Mark Martinec wrote:
> If not in v320.pre then it must be in some other .pre file.
> As Benny Pedersen noted your log shows that this plugin is enabled.
> Perhaps in /etc/spamassassin/sa-compile.pre .
The Rule2XSBody plugi
>UPDATE: I figured-out how to run a command-line scan using 'spamassassin
-D'
>which showed that it was using the old c.2011 rules in
/var/lib/spamassassin/3.003001/saupdates_openprotect_com. How do I fix
that?
If you have no intention to use 3rd party rules, I think you can just delete
that dir
I've just inherited an incoming SMTP relay running CentOS 5 with postfix,
Amavis and Spamassassin 3.3.1. We're using a daily cron job to run
sa-update and save the verbose result to a log file. The log doesn't have
much information but that seems to be a limitation in sa-update's output,
e.g. -v
On Tuesday 20 January 2015 20:17:57 Mark Martinec wrote:
> It may be worth trying with the current trunk version from SVN
> (a would-be-3.4.1), as Kevin suggested, so that we'd be on the same
> page.
>
>
> http://wiki.apache.org/spamassassin/DevelopmentStuff :
>
>The code itself is maintaine
On Tuesday 20 January 2015 18:30:18 Mark Martinec wrote:
> If not in v320.pre then it must be in some other .pre file.
> As Benny Pedersen noted your log shows that this plugin is enabled.
> Perhaps in /etc/spamassassin/sa-compile.pre .
The Rule2XSBody plugin is loaded on ubuntu in sa-compile.pre.
sorry!!
the compilation and installation were succesfully!
thank you
2015-01-21 12:24 GMT+01:00 Carlo Filippetto :
> Thank you,
> but how can I remove 'the new IO::Socket::IP' from cpan?
>
> other questions:
> - I have to try to update my perl version?
> - you say that them are only warnings a
Thank you,
but how can I remove 'the new IO::Socket::IP' from cpan?
other questions:
- I have to try to update my perl version?
- you say that them are only warnings and I don't need to use IPv6, how can
I go on installing spamassissin skipping those warnings?
thank you
2015-01-20 18:2
12 matches
Mail list logo