similar to: yum upgrade on 3.4 and spamassassin

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

Hello, CentOS 5.0 on x86_64 I'm trying to set up Xen paravirt guests with access to 2 block devices: One for / and one for swap. The block devices are LVM LVs, but that shouldn't matter. When I create the guest using either virt-manager or virt-install, I get asked which device to use for xvda. But I want more block devices: xvdb for swap. I know how to add this as an option to the

Hello, Anyone running rrdtool 1.2 from Dag's RPMs on CentOS 3 or 4? Been using 1.0, thinking about upgrading. Thx, -- Francois Caen, RHCE, CCNA SpiderMaker, LLC

Hello, Is there any difference between none and static for bootproto? Thx, -- Francois Caen, RHCE, CCNA SpiderMaker, LLC -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20060602/97344604/attachment-0002.html>

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

Hello, I encountered a problem when upgrading from 3.3 to 3.4 on i386. The machine is a production name server running bind. Looks like the new rpm moved my named.conf to .rpmsave and chkconfig'ed bind to off. That's really bad. A more gentle behavior would have been to save the new named.conf to .rpmnew and not mess with initscripts. Anyone else notice that? Francois Caen

Well, the first day was interesting. We a variety of questions from why do we do this, what's going on with RH, how come this is the first I've heard of you. And hundreds more. The good thing is that we've recieve a very positive response from everyone that visited our booth. Such a positive response that all our CentOS CD's are gone, and most of the cAos CD's are gone, and

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

Hello all, Do you guys use NFS v4 in production? Is the Linux implementation ready enough? The feeling I'm getting by looking at RH doc and other web sites is that v4 was added in a hurry and is not mainstream yet. I don't want to use something too cutting edge that will break down the road. Is that the case? In my case, it would be a CentOS5 server with CentOS4 client. Thanks, --

Look for consultant (for fee is acceptable) to provide step-by-step setup of DNS (forward & reverse) through the graphical interface of CentOS. Current setup is qmail server on static ip being nat''d through router. Need to setup for full DNS including PTR. Please contact - Beth Curotto American Business Networking, Inc 800-818-3244 -------------- next part -------------- An HTML

Any chance we can set up a low-volume "centos-announce" list so that we all don't have to read all of these non-Centos-specific E-mail threads about people figuring out how to admin a Linux box when all we need to know is when major releases/milestones/news items are available? Regards, -Tom

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

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

Hello, Anyone running cpanel on CentOS3.4, could you please tell me what you see at the top right corner of your WHM, where the version numbers are listed? Do you have "RedHat Enterprise 3 i686" like on RHEL or is cpanel aware that it''s CentOS? Thanks, Francois