similar to: Postgrey not working

On 2019-06-19 04:01, Nicolas Kovacs wrote: > Hi, > > I have a working installation of Postfix and Dovecot that works nicely. > I've added SpamAssassin, which does a good job of flagging spam. Now I > wanted to add greylisting to my server. > > Here's what I did. > > $ sudo yum install postgrey > > Increase the greylisting delay. > > #

On 19/06/2019 09:01, Nicolas Kovacs wrote: > Hi, > > I have a working installation of Postfix and Dovecot that works nicely. > I've added SpamAssassin, which does a good job of flagging spam. Now I > wanted to add greylisting to my server. > > Here's what I did. > > $ sudo yum install postgrey > > Increase the greylisting delay. > > #

Le 19/06/2019 ? 22:05, Phil Perry a ?crit?: > Try following the Postgrey guide on the Wiki: > > https://wiki.centos.org/HowTos/postgrey#head-314ceecc5ece27e0f0a4bf1abcd8ee9356cd1a5e > > > Works for me (allowing for the switch to systemd) I've followed this document, and still no joy. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730

Hi Guys, Are you interested in a brief guide on how to set up postgrey (anti-spam greylisting) with postfix? I set it up today and it took me a while to get it working as the config is slightly different from that on many of the googled guides (many are debian/ubuntu based). The darn config file lives in /etc/sysconfig on RH/CentOS rather than /etc/default as mentioned in all the guides I

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

Hello all, I am looking for the correct way to add postgrey to my system but whitelist everything except for com, org, and net domains. Most of my spam is from .info domains. There seems to be no way to only go after certain domains, instead postgrey wants to go after everything except what you whitelist. So my idea was to whitelist .com, .net, .org, .gov, and a few others while greylisting

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

Hi, We have implemented postgrey (postgrey-1.24, compiled from source package) on a centos 4.3 server. It works except for the whitelistings, in file postgrey_whitelist_clients, no matter what domain we enter, their incoming mails gets greylisted. I have posted this question to postgrey list but have not received anything yet. I works OK on a centos 4.1 server. Has anyone experienced similar

On Thu, Jun 11, 2020 at 05:02:03PM +0800, Plutocrat wrote: > On 11/06/2020 16.26, Marc Roos wrote: > > I know it is not dovecot who should fix this. But anyone using dovecot > > is using an MTA, and receiving spam ;) I know how to look at email > > headers. Spf and dkim is not solving anything here. > > You can configure this sort of thing in postfix, exim etc. The

Hi Karanbir, everyone I've only just noticed that the sections on Reporting, Multiple MX Considerations and Whitelisting on the Postgrey page are specific to postfix/postgrey. I remember we previously talked about making that page less specific to any particular MTA, and Steve has since kindly contributed a section for sendmail. So I'm wondering how we could best restructure the page

Package: logcheck-database Version: 1.2.35 Severity: minor logcheck-database contain postgrey ignore file, but postgrey first attempt is listed in logcheck report $ dpkg -l postgrey ii postgrey 1.18-1 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.29-C3EZRA Locale: LANG=it_IT,

Hi folks: I've recently migrated one of my production servers (bad Jason!) from WBEL to CentOS 3.3 using Donavan's instructions in the FAQ (http://www.centos.org/modules/smartfaq/faq.php?faqid=19). While it was as painless as the document suggests, I've run into problems with postgrey (a postfix greylisting daemon) on my server. Whenever I try to start postgrey, I get the

> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Gabriele Pohl > Sent: Friday, April 22, 2016 11:53 AM > To: centos at centos.org > Subject: [CentOS] output of "ls" (was: Re: Postgrey on CentOS 6) > > 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: > https://admin.fedoraproject.org/pkgdb/package/rpms/postgrey/ > > 1. Will I have to make an upgrade of the existing

Hi folks, I have installed postgrey from the rpmforge repo, but it does not work well with postfix from CentOS 5.2: I always get the error: warning: connect to postgrey/socket: Permission denied problem talking to server postgrey/socket: Permission denied But the permissions on the socket seem okay (postfix could write to it): srw-rw-rw- 1 postgrey postgrey 0 4. Okt 14:48 socket I

Hi, all. I want to use grey list in mail server, currently, i use postgrey to implement it. Any other recommended software? Thanks very much. ----- Best Regards. Zhang Huangbin - OpenBSD 4.2 -release, i386. - RHEL 5.1

hi guys, I tried installing postgrey but im having some troubles. #yum install postgrey Setting up Install Process Setting up repositories Reading repository metadata in from local files Reducing Dag-RHEL-Yum to included packages only Finished Parsing package install arguments No Match for argument: postgrey Nothing to do Anyone tried this one ? tnx --------------------------------- Do

I did some more digging around and found this is reproducible on multiple hosts running the same version of Dovecot/Pigeonhole/Postfix. The problem resurfaces on any host to an account with enabled Vacation/OOO response. The Vacation/OOO reply filter was created in Roundcubemail, but has been fine for years. One thing to note is in Dovecot 2.3.0 I did enable UTF8, but even if I disable UTF8

Package: logcheck Version: 1.2.57 Severity: normal Tags: patch In ignore.d.server/postgrey, change: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postgrey(\[[0-9]+\])?: action=.+, reason=.+, (delay=.+, )?client_name=.+, client_address=.+, sender=.*, recipient=.+ to: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postgrey(\[[0-9]+\])?: ([0-9A-F]+: )?action=.+, reason=.+, (delay=.+, )?client_name=.+,

Le 20/06/2019 ? 11:28, Alexander Dalloz a ?crit?: > What is being logged when a message passes your MTA inbound? The answer > to your issue is within the maillog. According to maillog, the message is delivered instantly, exactly like on a normal configuration without Postgrey. -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site :