similar to: postscreen and clamav on CentOS 6.8

Am 12.08.2016 um 22:38 schrieb Jon LaBadie: > A friend runs 6.8 but would like to add postscreen > to his email server. It is provided with postfix > version 2.8 and up. The newest postfix for 6.8 > is 2.6.x. Any likelyhood it will be further > updated? Or is there another source for newer > postfix versions for CentOS 6.8? > > Similar query for the clamav db, now at

On 08/12/2016 03:38 PM, Jon LaBadie wrote: > A friend runs 6.8 but would like to add postscreen > to his email server. It is provided with postfix > version 2.8 and up. The newest postfix for 6.8 > is 2.6.x. Any likelyhood it will be further > updated? Or is there another source for newer > postfix versions for CentOS 6.8? > > Similar query for the clamav db, now at

> Date: Saturday, May 14, 2016 16:20:41 -0700 > From: Alice Wonder <alice at domblogger.net> > > On 05/14/2016 01:22 PM, Walter H. wrote: >> Hello, >> >> just curious; >> since March 3rd, 2016 everdays logwatch-mail >> shows this: >> >> Last Status: >> WARNING: Your ClamAV installation is OUTDATED! >> WARNING:

Hello, just curious; since March 3rd, 2016 everdays logwatch-mail shows this: Last Status: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.99 Recommended version: 0.99.1 on May 4th, 2016 I updated clamav by yum update clamav since then the daily logwatch-mail shows this: Last Status: WARNING: Your ClamAV installation is OUTDATED! WARNING: Local

Jun 10 15:47:01 h2580013.stratoserver.net freshclam[1668]: Your ClamAV installation is OUTDATED! Jun 10 15:47:01 h2580013.stratoserver.net freshclam[1668]: Local version: 0.99.1 Recommended version: 0.99.2

On 09/07/2016 14:15, Walter H. wrote: > On 09.07.2016 14:39, Pete Geenhuizen wrote: >> I don't see it either. >> >> On 07/09/16 08:36, Walter H. wrote: >>> On 07.07.2016 22:19, Helmut Drodofsky wrote: >>>> Helo, >>>> >>>> update is in EPEL repository. >>>> >>> strange, here it isn't ... > the reason:

I don't see it either. On 07/09/16 08:36, Walter H. wrote: > On 07.07.2016 22:19, Helmut Drodofsky wrote: >> Helo, >> >> update is in EPEL repository. >> > strange, here it isn't ... > > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos

Hi, I administer a postfix mail server on CentOS 6. Now I want to setup another with similar configuration. But the postgrey package is no longer available in Epel for this CentOS release as I have seen now: https://admin.fedoraproject.org/pkgdb/package/rpms/postgrey/ 1. Will I have to make an upgrade of the existing mail server to get security patches again or is it not critical to use

EPEL maintainers? I note messages in the log about updated version 0.99.1 of CLAMAV being available since Mar 5th. for CentOS 6 no update is available yet. I used to use rpmforge for this package but that languished for months before updates became available and eventually stopped altogether. Is there something I can do to assist in getting this package updated? I have no idea if this is a

On Sat, 23 Apr 2016 02:23:28 +1200 Peter <peter at pajamian.dhs.org> wrote: > On 23/04/16 02:13, Gabriele Pohl wrote: > > I administer a postfix mail server on CentOS 6. > > Now I want to setup another with similar configuration. > > > > But the postgrey package is no longer available in Epel > > for this CentOS release as I have seen now: > >

On 03/04/16 22:10, Ireneusz Piasecki wrote: > W dniu 03.04.2016 o 04:39, Rob Kampen pisze: >> EPEL maintainers? >> I note messages in the log about updated version 0.99.1 of CLAMAV >> being available since Mar 5th. >> for CentOS 6 no update is available yet. >> I used to use rpmforge for this package but that languished for months >> before updates became

Hello gents, First time poster here! Current system running Centos 6.8. Buddy of mine posted a few days back about me wanting to move from Postfix 2.6.x to 2.8 to above, still under centos 6.8. I might move over to 7, but probably not for a while, don't have the resources presently to make this happen. Running Centos 6.8, postfix 2.6.6, clamav 0.99.1. Basic Centos 6.8 box fully patched

Helo, update is in EPEL repository. on startup, clamd does not further create clamd.sock and clamd.pid clamd service stops without any message - even in debug mode. It's a nightmare. Helmut -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart Gesch?ftsf?hrung Dr.-Ing. Roswitha Hahn-Drodofsky HRB 21091 Stuttgart USt.ID: DE190582774 Tel. 0711

On 3/31/2017 2:15 PM, Valeri Galtsev wrote: > Well, it sounds like you are one of the companies with whose effort I have > to fight constantly in my own effort to protect our users from spam... What makes Postfix superior in fighting spam? How do I integrate MIMEDefang, SpamAssassin, and ClamAV with Postfix? Are there migration guides for moving one's Sendmail anti-spam and AV

Hi, I'm currently busy with a substiution of my current mail server. I'm currently using * Clam-SMTP and * SpamAssassin to fight Spam. I wonder if it is worth implementing AmaViS with SpamAssassin backend instead and also using AmaViS to speak to clamd directly. But I more and more wonder wether AmaViS is even worth it?! It currently looks to me as if AmaViS is eating LOTS of

Hi, I'm currently fine-tuning my mail server (Postfix and Dovecot on CentOS 7). SPF, DKIM and DMARC work fine, now I'd like to limit the spam tsunami. Besides the official Postfix documentation, I've read a few articles about Postfix spam restrictions, namely these : https://www.linuxbabe.com/mail-server/block-email-spam-postfix https://wiki.centos.org/HowTos/postfix_restrictions

I think something along these lines appeared before but I was unable to find them. I'm on a 7.6 system, been running clamav and amavisd-new since 6 days with little problem. On a recent reboot, clamd at amavisd does not start up and fails manual start. The problem seems to be the missing socket that connects the pair, "/var/run/clamd.amavisd/clamd.socket". I believe this should

On Sun, May 15, 2016 at 02:55:01AM +0000, Richard wrote: > > > Date: Saturday, May 14, 2016 16:20:41 -0700 > > From: Alice Wonder <alice at domblogger.net> > > > > On 05/14/2016 01:22 PM, Walter H. wrote: > >> Hello, > >> > >> just curious; > >> since March 3rd, 2016 everdays logwatch-mail > >> shows this: >

Hi all, Just out of curiosity: is there anything we can do, on the samba side, to counter the recent ransomware attacks? (or limit the damage done) I'm thinking like: limit the number of files per second a client (workstation) is allowed to edit, or some other smart tricks..? It would be nice if samba could be an extra layer of defense. Something perhaps a vfs module could help with..?

My nightly logwatch report had a never before seen section last night, "barracuda spam firewall". I have not problem with the emails it noted as being rejected. But I've always thought of "barracuda" as a commercial product. I have neither configured nor enabled any barracuda software and "yum list '*barrac*'" comes up empty. What is this? Jon -- Jon