search for: spamassassin

pulling my hair out... If I rm -fr /root/.spamassassin/* then sa-learn a bunch of messages, it works... ]# sa-learn --dump magic 0.000 0 3 0 non-token data: bayes db version 0.000 0 3997 0 non-token data: nspam 0.000 0 0 0 non-token data: nham 0.000 0 202022...

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 sendma...

Hi, As there is no (decent) way to specify a particular repo for an particular package with yum, I'm having an odd problem: Although the version numbers differ, I have 2 spamassassin pkgs in different repo's (updates and my own addons) which are seen as updates to eachother: jelsum:/root-# tail -11 /var/log/yum.log Sep 02 04:26:34 Installed: perl-Mail-SpamAssassin.i386 3.1.0-1 Sep 02 04:26:35 Updated: spamassassin.i386 3.1.0-1 Sep 03 05:01:36 Obsoleting: spamassassin.i386...

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<------------------------------------------------------------...

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 head...

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

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 e...

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/p...

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 install/upgrade these to satisfy the dependencies: [deps: perl-Ti...

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...

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 to stay with RPM's rather than amending software directly. Also, many of these responses are over 10 years old, so I'm a little sc...

...be updated ---> Package mtr.i386 2:0.71-1.el4.rf set to be updated ---> Package iptraf.i386 0:3.0.0-1.2.el4.rf set to be updated ---> Package nmap-frontend.i386 2:4.01-2.2.el4.rf set to be updated ---> Package python-urlgrabber.noarch 0:2.9.7-1.2.el4.rf set to be updated ---> Package spamassassin.i386 0:3.0.5-3.el4 set to be updated ---> Package nmap.i386 2:4.01-2.2.el4.rf set to be updated ---> Package rsync.i386 0:2.6.7-2.el4.rf set to be updated ---> Package lftp.i386 0:3.4.4-1.el4.rf set to be updated ---> Package freetype.i386 0:2.1.9-1.2.2.el4.rf set to be updated --->...

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

Hello fellow CentOS-users, on the net there are lots of Spamassassin related HOWTOs - describing how to create a shell script for Postfix and how to install Spamassassin and start its spamd daemon - step by step. Additionally antivirus setups are described... But I have a strong feeling, that this is unneeded on CentOS 6 - because there are already preconfigured st...

...nburn 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 cures. >> >> Before I start changing things I was wondering if there was a Centos 7 >> specific resolution. Where possible, on production machines I prefer >> to stay with RPM's rather than amending software directly. > > I run SpamAssassin on CentOS 7;...

On 12/12/2017 04:37 AM, Nicolas Kovacs wrote: > Spamassassin has been working nicely on my main server running CentOS 7 > and Postfix. SELinux is activated (Enforcing). > ... > SELinux is preventing /usr/bin/perl from 'read, write' accesses on the > file /var/log/spamassassin/.spamassassin/bayes_toks. > ... > Source Context...

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 entirely.. Or.. Whitelist logwatch. Apparently, I am gu...

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_P...

Hi, My mail server is running on CentOS 7 with Postfix, Dovecot and Spamassassin. I get quite a lot of spam on a few accounts, and Spamassassin does its job fine. Spam mail is identified correctly, and it looks like there are no false positives, e. g. valid mail is never identified as spam. When a message is flagged as spam, the subject line is rewritten to begin with [SPAM]....

...100% |=========================| 951 B 00:00 extras 100% |=========================| 1.1 kB 00:00 Reading repository metadata in from local files Resolving Dependencies --> Populating transaction set with selected packages. Please wait. ---> Package spamassassin.i386 0:3.0.4-1.el4 set to be updated --> Running transaction check --> Processing Dependency: perl-Mail-SpamAssassin = 3.0.2-1 for package: spamassassin-tools --> Finished Dependency Resolution Error: Missing Dependency: perl-Mail-SpamAssassin = 3.0.2-1 is needed by package spamassassin-to...