similar to: SpamAssassin training plugin

Hi, We recently made the switch to 1.9 for our large rails 2.3.14 project and ran into some strange behavior from the unicorns where encoding problem would cause blank 500 pages to be "randomly" served to users (we run ~10 x 5 unicorn workers behind our load balancer). We found that unicorn workers were dying when someone requested a url with utf-8 in it, and died in such a way that

Hello, I'm building a couple of mixed models using the lmer function. The actual modelling is going well, but doing some reading on the use of crossed random effects and the comparison of models with and without random effects it is clear that I need to generate some Markov Chain Monte Carlo samples. However, I'm struggling because everyone time I go to generate a sample I get the

How do I get this set up? spamassassin -D --lint shows me an error... debug: bayes: no dbs present, cannot tie DB R/O: /root/.spamassassin/bayes_toks and with no db present, it doesn't learn. Is there something simple that I'm missing? Craig

Hi, Spamassassin has been working nicely on my main server running CentOS 7 and Postfix. SELinux is activated (Enforcing). Since the most recent update (don't know if it's related to it though) I'm getting the following SELinux error. --8<----------------------------------------------------------------- SELinux is preventing /usr/bin/perl from 'read, write' accesses on

greetings, have been google foo for week or so. used to be super easy to upgrade spamassassin on CentOS dist. just grab the tarball and put in right spot and rpmbuild -tb spamassassin-3.somethingsomething.tar.gz then rpm or yum install and done would take just a few minutes. Yet... in regards to EL4 / CentOS 4 and spamassassin, it appears the end of the road for .spec in SA tarball

I wonder if anyone is actually running SpamAssassin with Postfix/Amavisd-new under CentOS-6.4 . I have followed the instructions in <http://wiki.centos.org/HowTos/Amavisd> but as far as I can see SpamAssassin is not working. I should say that I do not understand from this document what is meant to happen to spam. I understand that a Spam header is added, but what actually happens to email

Hello, I run CentOS 3.4 on 3 machines (i386). Original yum.conf If I do a yum update: No actions to take If I do a yum upgrade a machine that has no spamassassin: No actions to take If I do a yum upgrade on 2 machines that have perl-Mail-SpamAssassin-3.0.1-1 installed (3rd party rpm, more recent than the CentOS/RHEL one): I will do the following: [update: spamassassin 2.55-3.4.i386] I will

I have installed spamassassin, per the instructions on Scalix's wiki, and it is working, with some important caviats. So I asked for help on the spamassassin user list, and got some, but I think I am butting up against some Centos specific issues... This is what I am seeing in the maillog: Aug 17 14:39:59 z9m9z sendmail[13082]: l7HIdvGf013082: Milter add: header: X-Spam-Checker-Version:

Postfix 2.5.5 SpamAssassin 3.2.5 (under Perl 5.10.0) ClamAV 0.95.1 Dovecot 1.2.rc2 works fine on Fedora 10. Installed Dovecot and ClamAV from source and everything else using yum. I'm using the ClamAV plugin for Spamassassin: http://wiki.apache.org/spamassassin/ClamAVPlugin I'm calling Spamassassin with: /etc/postfix/main.cf: mailbox_command = /usr/bin/spamc -f -e

Hi, I recently saw this a branch [1] of your git repository when dovecot-antispam has support of spamassassin. Is it intentional to not add it to the official release? Are there any plan to officially support spamassassin? [1] http://www.freenux.org/cgi-bin/gitweb.cgi?p=dovecot-antispam.git;a=shortlog;h=refs/heads/spamassassin Thanks -- Yann

I have the following error message in my /var/log/spamd spf: lookup failed: available_nameservers: No DNS servers available! Having Googled the error message I've found a number of responses which involve patching Perl or Spamassassin or other cures. Before I start changing things I was wondering if there was a Centos 7 specific resolution. Where possible, on production machines I prefer

Dear Friends, I executed yum upgrade and yum show that there is dependency spamassassin-tools, but I have installed. See LOG YUM [root at srv001 qmailscan]# yum update Setting up Update Process Setting up repositories kbs-CentOS-Extras 100% |=========================| 951 B 00:00 update 100% |=========================| 951 B 00:00 dag

Is there any good rpm source for latest spamassassin for centos/rhel ? Currently using from dag's, but is is a bit old version nowdays. -- Eero

Hi all, Well it took a while for me to figure it out, but apparently my logwatch no longer can be mailed locally on my computer as I believe spamassassin is eating it. I can send it out to an email address outside my server though. So spamassassin is only checking incoming I guess. My question is....how do I...or should I.... Make all local mail go straight to the boxes and skip spamasassin

A patch has been proposed for SpamAssassin to process Maildir folders of spam: <https://issues.apache.org/SpamAssassin/show_bug.cgi?id=3003> Is this patch compatible with Dovecot's implementation of Maildir? For example, is anything needed to avoid stepping on Dovecot's metadata?

Hi, is there everywhere an spamassassin-3 rpm? tia

On 10/08/17 15:37, Paul Heinlein wrote: > On Thu, 10 Aug 2017, Gary Stainburn wrote: > >> I have the following error message in my /var/log/spamd >> >> spf: lookup failed: available_nameservers: No DNS servers available! >> >> Having Googled the error message I've found a number of responses >> which involve patching Perl or Spamassassin or other

Hello, I may be a little confused but why is there a spamassassin package and a spamassassin perl module? Which is better? It looks like the perl module version has more plugins. What if I have both installed? TIA

Guys, What repo has rpms for mailscanner, clamav and spamassasin?

The spamassassin on my server is 3.2.5 and is stock CentOS 5.x. I do apply updates regularly. Most of my legitimate contacts are either whitelisted or sorted into folders before spamassassin sees them, but I have noticed an increasing amount of legitimate mail marked as spam. One issue seems to be the FH_DATE_PAST_20XX rule. I was able to fix that via running sa-update as root per