Matt wrote:
> I'm drawing a blank, and couldn't find anything in the Wiki. Where, in
> SA 3.x, do you setup/configure URL blacklist checking?
/etc/mail/spamassassin/init.pre
# URIDNSBL - look up URLs found in the message against several DNS
# blocklists.
#
loadplugin Mail::SpamAssassin::Plugin
I'm drawing a blank, and couldn't find anything in the Wiki. Where, in SA
3.x, do you setup/configure URL blacklist checking?
On Apr 18, 2007, at 4:26 PM, Robert Fitzpatrick wrote:
Thanks, we are rebuilding bayes and now have in SQL with auto learn
on, is that good? Now has over 25K spam, but just 180 ham.
You *really* want to train with more ham than spam.
-faisal
On Tue, April 17, 2007 18:09, Benny Pedersen wrote:
> forwarded mails should olso be tested agaist spamhaus :(
since no comment here i make it into a bug
http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5426
any comment now ? :-)
--
This message was sent using 100% recycled spam mails.
On Wed, 2007-04-18 at 10:23 -0500, Craig Carriere wrote:
> Robert:
>
> It sounds like your problem rests with your bayes database. Some SA
> rules will fire on almost all mail, but a properly trained bayes filter
> should be able to reduce your scores to under your spam threshold. None
> of thes
We've been getting massive amounts of backscatter spam, large amounts of
which is making it past SA. Most of it isn't making any real effort to
disguise the fact that it didn't originate from our outbound systems,
and I've been looking at the VBounce plugin to help stop it.
The plugin recomme
NFN Smith wrote:
> Jake Vickers wrote:
>
> > It's in your RDJ config file. My config is in /etc/rulesdujour/ and
> > the
> > file is called "config". The line in question:
> > SA_DIR="/etc/mail/spamassassin"
> > That's where it should save the files it downloads.
>
> I checked the code of rules_
At 07:37 18-04-2007, Michael Scheidell wrote:
Trouble is, I don't know if all the TLD's are supposed to have records
for mail.global.frontbridge.com or not.
Ask the nameservers which are authoritative for mail.global.frontbridge.com:
frontbridge.com.172800 IN NS ns10-f.bigfi
> -Original Message-
> From: Dan Barker [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 18, 2007 11:02 AM
> To: users@spamassassin.apache.org
> Subject: RE: How to workaround RFCI / DNS issue with
> frontbridge clients?
>
> I don't know what's wrong with your nslookup, but dig is
Robert:
It sounds like your problem rests with your bayes database. Some SA
rules will fire on almost all mail, but a properly trained bayes filter
should be able to reduce your scores to under your spam threshold. None
of these scores rate out very aggressively so I am surprised that these
are
Our bayes was apparently giving negative scores incorrectly and I
re-built it since it was not effective and letting through a lot of
spam. I didn't realize, but it seems those negative scores were keeping
SA from applying other tests? Since fixing bayes, we are blocking so
much ham it is not funny
I don't know what's wrong with your nslookup, but dig is fine. Both return
the same up to the final results.
[EMAIL PROTECTED]:~$ dig +trace mail.global.frontbridge.com
; <<>> DiG 9.2.2-P3 <<>> +trace mail.global.frontbridge.com
;; global options: printcmd
. 85975 IN
I like RFCI blacklists.. I use RFCI, I don't want to debate it, you
don't have to use them if you don't like them. You can set all the
scores to 0 if you won't want to use it.
I have a minor (DNS?) issue that might involve every frontbride client
in the world, and anyone using RFCI bogusx MX black
On Wed, 18 Apr 2007, Bill McCormick wrote:
Duane Hill wrote:
On Wed, 18 Apr 2007, jpff wrote:
Well the SARE_* rules come from the SARE rulesets over at
rulesemporium.com, which sa-update does NOT update. sa-update, by
default, updates the official ruleset only.
Not true; I update the SA
jpff wrote:
Much to my regret I am having to abandon use of spamassassin. If I
include it in my mix (exin/spamassassin/clamav) then as soon it there
is a flurry of mail I get timeouts from spamd, and then errors about
deleteing unallocated memory in spamassassin, and no mail is
delivered. This
Duane Hill wrote:
On Wed, 18 Apr 2007, jpff wrote:
Well the SARE_* rules come from the SARE rulesets over at
rulesemporium.com, which sa-update does NOT update. sa-update, by
default, updates the official ruleset only.
Not true; I update the SARE runs using sa-update
So you are saying
This is generally a good idea and can be easily accomplished in Exim.
Just add the following condition to your spam checking ACL.
condition = ${if <{$message_size}{500k}{1}{0}}
Or be even more radical and limit it to the 200-250K recommended by SA.
Loren
Jean-Paul Natola wrote:
My most recent discovery was SA hanging on huge attachments ( from
web-designers) , I'm currently TRYING to modify Exim to NOT send messages
over 500k to SA- as most spam is usually just a few k-
This is generally a good idea and can be easily accomplished in Exim.
J
Maybe your spamassassin taking too much cpu or have some "out of memory"
problem...
See this tips to get spamassassin to run faster/better:
http://wiki.apache.org/spamassassin/FasterPerformance
Sebastian Ries escreveu:
Hi
I have this problem about once a month:
Spamassassin works without
On Wed, 18 Apr 2007, jpff wrote:
Well the SARE_* rules come from the SARE rulesets over at
rulesemporium.com, which sa-update does NOT update. sa-update, by
default, updates the official ruleset only.
Not true; I update the SARE runs using sa-update
So you are saying just by typing 'sa-upd
jpff writes:
> I tried switching bayes off and it has run for 4 hrs before the
> failing starts again
>
> Apr 18 08:16:37 snout spamd[29102]: spamd: copy_config timeout, respawning
> child process after 1 messages at /usr/bin/spamd line 968.
> Apr 18 08:16:46 snout spamd[29096]: spamd: copy_con
Hi all..
Sa dosent work like first day installation.Alot spam
mail
are passing.I run sa-update and these updates in
/var/lib/spamassassin/3.001008/updates_spamassassin_org
how can I sure my sa is recently updated and use
updates that in /var/lib ?
_
Hi
> > I have this problem about once a month:
> >
> > Spamassassin works without problem but suddnely spamd stops running.
> > All I see in the logfile is:
> >
> > Apr 11 13:12:56 extmail spamd[20273]: spamd: server killed by SIGTERM,
> > shutting down
>
> Are you sure you don't have some reaper
On Tuesday 17 April 2007, Sebastian Ries wrote:
> Hi
>
> I have this problem about once a month:
>
> Spamassassin works without problem but suddnely spamd stops running.
> All I see in the logfile is:
>
> Apr 11 13:12:56 extmail spamd[20273]: spamd: server killed by SIGTERM,
> shutting down
Are yo
Hi
I have this problem about once a month:
Spamassassin works without problem but suddnely spamd stops running.
All I see in the logfile is:
Apr 11 13:12:56 extmail spamd[20273]: spamd: server killed by SIGTERM,
shutting down
after that spamc cannot connect to spamd...
I don't find anything th
I tried switching bayes off and it has run for 4 hrs before the
failing starts again
Apr 18 08:16:37 snout spamd[29102]: spamd: copy_config timeout, respawning
child process after 1 messages at /usr/bin/spamd line 968.
Apr 18 08:16:46 snout spamd[29096]: spamd: copy_config timeout, respawning
c
26 matches
Mail list logo
