On Wed, Jan 13, 2010 at 8:53 AM, Geoff Soper
geoff.m...@alphaworks.co.uk wrote:
I've now added the saupdates.openprotect.com
channel which contains recommended SAREs rules and all is working!
I thought I read that no one should be using openprotect as it's
hoplessly out of date. ??
--
On Wed, Jan 13, 2010 at 10:11 AM, Geoff Soper
geoff.m...@alphaworks.co.uk wrote:
OK, I'm slightly confused as to what the advice is here. Is there consensus
on SAREs? Should I still use them (via the channel list described at
http://wiki.apache.org/spamassassin/SareChannels ) or is it better
Regardless of the reason, is my SA now broken, and in any case, how do
I recover from this?
--
-ste
I have two identically (or so I thought) configured mail servers, each
pulling down SARE rules (successfully, I might add). One of them shows
hits on SARE rules all the time - the other one, never. Aside from
simply configuring sa-update to pull the rules down, I'm wondering if
there is something
On 1/1/07, Shaun T. Erickson [EMAIL PROTECTED] wrote:
What am I doing wrong?
I just ran amavisd with the debug-sa option, and as near as I can
tell, it appears to only be using the original ruleset - and doesn't
even seem to know that I am pulling new rules down with sa-update.
I must have
On 1/1/07, Gary V [EMAIL PROTECTED] wrote:
You must be running SA 3.1.4 or older and amavisd-new 2.4.2 or older.
Nope. SA 3.1.7 amavisd-new 2.4.4.
I see in amavisd, the line you suggested I add is actually there, but
commented out, as a comment there indicates that SA should be able to
Ok. I'm starting to understand this now. I've built perl 5.8.8 and
pointed my existing amavisd-new at it, by editing its first line. I
then added, via CPAN, any module it complained was missing, each time
I tried to run it, until it no longer complained of anything missing
(that was required,
On 1/1/07, Gary V [EMAIL PROTECTED] wrote:
When you run amavisd debug-sa does it say you are using?:
Module Mail::SpamAssassin 3.001007
Yes.
Have you run 'sa-update'? I'm wondering if you have files in
/var/lib/spamassassin/3.001007/
Yes, I see stuff in there, and in the directories I
Ok, this is interesting. :)
I removed all SA installations, except for the one under /usr/local/perl-5.8.8.
I moved my sa-update-keys directory to
/usr/local/perl-5.8.8/etc/mail/spamassassin.
I modified my nightly script to use /usr/local/perl-5.8.8/bin/sa-update.
I ran my nightly script.
Now
On 1/1/07, Shaun T. Erickson [EMAIL PROTECTED] wrote:
Ok, this is interesting. :)
The follow-up to this is that I just got spam that was hit by the SARE
rules, so it's working now. Additionally, Razor2 DCC are now
working, as well. So the only mystery is why everything installed
where it did
I'm seeing hundreds of connection attempts from systems claiming to be
in the kntr top level domain, on a client's mailserver. I haven't seen
these on my own server. Is this new, or are they just finally getting
around to a server I admin, so I'm now noticing it? Anyone else seeing
this?
--
I've just downloaded this and set it up. I see there are MANY rulesets
I can choose from, but I have no idea if they are all 'safe' (not even
sure what I mean by that). Is there a subset of all these rulesets,
that everybody uses, or does everyone use all of them? How do you
decide which to use
On 10/29/06, Leander Koornneef [EMAIL PROTECTED] wrote:
If you are using spamassassin 3.1, you can use sa-update to get the SARE
rulesets from the channel provided by http://saupdates.openprotect.com/.
This negates the necessity to run rulesdujour alongside sa-update. This
channel consists only
On 10/29/06, Leander Koornneef [EMAIL PROTECTED] wrote:
In my experience, using the default sa-update channel, the openprotect
channel, auto-whitelisting, proper bayes training(!), pyzor, razor,
dcc, SPF
and DNS blacklists wil get you a spam detection rate 99%.
I'm doing all that, now, I
I am setting up a new server to replace an old one. The old server ran
a version of spamassassin prior to it's use of plugins.
I've got my new server up and running (CentOS 4.4) nicely, with
amavisd-new (v2.4.3) calling spamassassin (v3.1.7), and SA's default
settings are tagging most spam as
On 10/28/06, Theo Van Dinter [EMAIL PROTECTED] wrote:
On Sat, Oct 28, 2006 at 03:12:16PM -0400, Shaun T. Erickson wrote:
Yes, I've gone to the SA site, and read what I can find on these three
plugins, but it's still not clear to me how to enable them and see
that they are actually being used
On 10/28/06, Theo Van Dinter [EMAIL PROTECTED] wrote:
If you want to see Razor debug output, run a
message through in the way I mentioned before, ala:
spamassassin -D razor2 message_file /dev/null
will show you only razor2 debug output (most of which will look like output
from razor-check
On 10/28/06, Clifton Royston [EMAIL PROTECTED] wrote:
Did you run the discover mode on Razor yet? You need to manually
run that (as the user and with the home directory Razor will be running
as, in your case amavis) for it to latch onto some servers to use.
Yes, and Razor2 is working fine
On 10/28/06, Shaun T. Erickson [EMAIL PROTECTED] wrote:
The current problem is that Pyzor times out trying to contact it's
remote server:
Because this server (66.250.40.33:24441) - which I got from multiple
tries at running 'pyzor discover' - isn't responding. This one
(82.94.255.100:24441
Chris Santerre wrote:
http://www.packtpub.com/book/spamassassin
How does this book compare to the O'Reilly book, by Schwartz?
-ste
Martin Schröder wrote:
On 2004-10-07 10:37:32 -0400, Chris Santerre wrote:
http://www.packtpub.com/book/spamassassin
Release date November 1999
Yes, it should be at the press by now. :-)
Best regards
Martin
PS: If it applies to SA3, the description should mention that.
Hmm. When
21 matches
Mail list logo
