similar to: EL4 and spamassassin info

heads up and fyi folks... CentOS 4 latest... SpamAssassin version 3.3.1 running on Perl version 5.8.8 :-) i noticed on a centos 4 box after doing a manual yum update and getting 2 updated perl packages from rpmforge again, just a heads up as rpmforge has been rock solid for us for years so we are no bashing spamassassin would not restart after the updates.... spamd: Oct 27 22:32:01.340

One more bugfix since rc2: - Maildir: synchronization might have sometimes set wrong flags to messages, or crash completely Quite rare because we were lucky before :) And list of all the changes one more time: v0.99.10.5 2003-12-27 Timo Sirainen <tss at iki.fi> + MySQL authentication, patch by Matthew Reimer + --with-moduledir configure option - mbox: APPEND reversed given

greetings i have a newer centos 4.2 server using qmail for smtp the /etc/yum.conf has this in it exclude=spamassassin exim postfix sendmail so when i do a yum update to go to 4.3 i get this --> Running transaction check --> Processing Dependency: smtpdaemon for package: mdadm --> Finished Dependency Resolution Error: Missing Dependency: smtpdaemon is needed by package mdadm how

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

In http://wiki.centos.org/HowTos/Amavisd there is a recommendation to NOT use the version that comes with Centos 6.3, but to get the more current version from RPMForge. Is this the 'correct' thing to do on a Centos-based mail server?

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

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

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

we need to filter out various peoples posts on this list would some kind soul(s) please direct us in locating the best email list reading programs w/ the best features to read the centos and other lists. the CentOS list signal/noise ratio is so bad that we need something better than just outlook like clients or whatever appropriate windows and linux recommendations would be most appreciated

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