On Wed, 6 May 2009, ermille1979 wrote:
configuration file "/usr/share/spamassassin/20_advance_fee.cf" requires
version 3.002004 of SpamAssassin, but this is code version 3.02.
I would suggest you first try to fix this problem before looking at
anything else. It seems an SA upgrade was not
Ehm...yes ;-)
this is my file init.pre
# will affect how those files are parsed, like which plugins are loaded
# etc.
#
###
# RelayCountry - add metadata for Bayes learning, marking the countries
# a message was relayed th
ermille1979 wrote:
> Hi Matt!
>
> OH! Sorry..
>
> This is file correct
>
> This is My file local.rc
>
Hopefully you mean local.cf not local.rc :)
Also, can you check your init.pre and make sure it contains this line:
loadplugin Mail::SpamAssassin::Plugin::SPF
I think that may have to do with
Hi Matt!
OH! Sorry..
This is file correct
This is My file local.rc
###
#
# rewrite_header Subject *SPAM*
# report_safe 1
# trusted_networks 212.17.35.
# lock_method flock
report_safe 1
#required_hits 4
required_sco
ermille1979 wrote:
> Hi all,
>
> I have a problem with Spamassassin on my Qmail
>
Alex,
Can you explain why you think senders from agipro.it would be whitelisted?
The only whitelist option in the config you sent is commented out, so it
would have no effect.
Is the LOCAL_RCVD rule the one t
On 05.05.09 06:59, ermille1979 wrote:
> I have a problem with Spamassassin on my Qmail
>
> r...@mail/etc/mail/spamassassin rpm -qa|grep -i spamas
> perl-Mail-SpamAssassin-3.0.2-1
> spamassassin-3.0.2-1
> spamassassin-tools-3.0.2-1
Oh! that is way too old! I wonder if this still can catch any spam
