similar to: Centos 7 specific cure for Spamassassin DNS lookup problem

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

On Thursday 10 August 2017 18:45:32 Gordon Messmer wrote: > On 08/10/2017 01:21 AM, Gary Stainburn wrote: > > I have the following error message in my /var/log/spamd > > > > spf: lookup failed: available_nameservers: No DNS servers available! > > Try starting spamassassin later. Run "systemctl edit > spamassassin.service" and insert two lines: > >

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 cures. > > Before I start changing things I was wondering if there

On 08/10/2017 01:21 AM, Gary Stainburn wrote: > I have the following error message in my /var/log/spamd > > spf: lookup failed: available_nameservers: No DNS servers available! Try starting spamassassin later. Run "systemctl edit spamassassin.service" and insert two lines: [Unit] After=network-online.target

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:

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 stock packages for postfix and

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

I have a problem getting spamd and sendmail (both stock CentOS4 rpms) to work together on a couple of smtp relay machines. This is clearly a configuration issue and no doubt revolves around my lack of comprehension of how this is to work. Basically, the setup consists of two frontend public smtp transports that redirect all email through a firewall to an internal imap server for final

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 3 Mar 2017, Bernard wrote: > On 01/03/2017 11:27, Bernard wrote: >> Hello, >> >> I am new to the list. /Waving at everyone/ >> >> I got a basic SpamAssassin working on a Debian setup (w/ debian-spamd >> user), running as a Postfix transport. >> >> I am currently trying to switch it to a

Hello, I am new to the list. /Waving at everyone/ I got a basic SpamAssassin working on a Debian setup (w/ debian-spamd user), running as a Postfix transport. I am currently trying to switch it to a dovecot plugin in order to make it interactively work with the email storage (react to mail classification, being able to train it from already received emails, aso.) My problem is now making it

Check this out: % sa-update Subroutine NetAddr::IP::UtilPolluted::AF_INET6 redefined at /usr/lib/perl5/5.8.8/Exporter.pm line 65. at /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi/NetAddr/IP/Util.pm line 180 ******************************************************************************* Gilbert Sebenste ******** (My opinions

Hi all, I am trying to setup a mail server using postfix (virtual_mailboxes), spamassassin and dovecot, along with SQL where appropriate. From my research so far I realized that, for several reasons, it is required for me to use dovecot LDA instead of maildrop, local, procmail or other alternatives. My configuration was working flawlessly, until spamassassin per-user configuration came to

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

Package: logcheck Version: 1.2.26 Severity: wishlist Please add ignore for Spamassasin's "check" messages like: Aug 16 19:27:54 ns spamd[23853]: checking message <20040816150710.86ADA708A8 at smtp-out.hotpop.com> for nobody:65534. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.4.26.20040601 Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL

On 2017-03-03 10:26, Bernard wrote: > No help there? > --- > Bernard > > On 01/03/2017 11:27, Bernard wrote: >> Hello, >> >> I am new to the list. /Waving at everyone/ >> >> I got a basic SpamAssassin working on a Debian setup (w/ debian-spamd >> user), running as a Postfix transport. >> >> I am currently trying to switch it to a

I am running a server with Centos 4.4, using a combo of sendmail-clamav-spamassassin for mail, which has been working quite well up until last night. Around 3:00am, all mail going to all users was being rejected by spamassassin. My ~/mail/.procmailrc is as follows: ======================== MAILDIR=$HOME/mail # :0 H * ^X-Spam-Status:.*Yes { EXITCODE=67 :0: /dev/null } =========================

I've been messing with this for too long, now, and I'm blind to whatever's wrong. Or I'm simply being dense. Either way, I need help with a common issue. I'm trying to get Postfix+Spamassassin+Dovecot going on Fedora 10. (I'll get back to the global Sieve thingy soon, but I need to get this going, first.) When using the simple: mailbox_command =

I've just set up a new mailserver using Centos5.2 (sendmail+clamav-milter+spamass-milter). I'm using the spamass-milter package from rpmforge (spamass-milter-0.3.1-1.el5.rf). I notice that the default setup is to run it as root. I set up my previous mailserver on Centos4, and I can't remember if I did anything special, but on that machine it runs as user "sa-milt". Is

Package: logcheck-database Version: 1.2.43a Severity: minor Since last weekend's upgrade of logcheck-database from 1.2.42 to 1.2.43a, logcheck stopped ignoring routine SpamAssassin messages of the form Feb 20 21:36:16 tux64 spamd[4665]: spamd: checking message <20060220190721.0E0B41C5207 at llwb563.servidoresdns.net> for amu:7286 Could you please edit the second pattern in