Greylisting unavailable / can not configure

9 posts / 0 new
Last post
#1 Fri, 09/14/2018 - 12:20
KAtwitch

Greylisting unavailable / can not configure

When I go to the "email greylisting" section of Virtualmin, I see a message that, "Greylisting is not available on this system : The Postgrey user postgrey does not exist However, Virtualmin can attempt to automatically install the Postgrey greylisting package for you." I select the option to "install Postgrey now" and receive the following:

Loaded plugins: fastestmirror, refresh-packagekit, security
Setting up Install Process
Loading mirror speeds from cached hostfile
* base: mirror.tzulo.com
* epel: mirror.steadfastnet.com
* extras: mirror.trouble-free.net
* updates: repo.miserver.it.umich.edu
Package postgrey-1.34-1.noarch already installed and latest version
Nothing to do
.. install complete.
.. installation failed!
<!--break-->
Postgrey will start with this command on CentOS.  No apparent issues:
[root@zoe ~]# /etc/init.d/postgrey start
Starting postgrey:                                         [  OK  ]

I'm at a loss. This appears to be a virtualmin config issue, especially since postgrey is running.

Tue, 09/18/2018 - 14:45
KAtwitch

Bump. Anyone?

Mon, 09/24/2018 - 08:00
KAtwitch

Bump

Wed, 01/23/2019 - 10:07
amityweb

Did you figiure this out? Decided to enable greylisting, but then this! Its been an option on the server for years, so I thought it would at least just work. But I get the above message. postgrey is showing in Bootup and Shutdown actions, I have set it to start and to start on boot, and then run "service postgrey start" which says OK, but then it shows the above message on the Greylisting page in Virtualmin.

Is it running? Is it working? Are there supposed to be settings? Do we need to create a postgrey user as it states?

Thanks, anyone.

Wed, 01/23/2019 - 10:12
amityweb

Got it working, I hope...

First manually created the user postgrey in group postgrey

Still did not work, athough I have a different message saying Greylisting is not enabled, and click the button to enable it. But clicking the button did nothing, same message.

So I did "yum remove postgrey" then "yum install postgrey" then when I click Enable Greylisting on the Greylisting page it worked.

So guess the install process using Webmin has some issue. It does not even create the postgrey user which I guess needs to happen first.

Wed, 01/23/2019 - 10:32
amityweb

Sigh... doesnt work anyway. All looks like its working, can see the settings page (with whitelisting options on), postgrey is running, smtpd_recipient_restrictions has it in the config, see below, BUT... emails are coming through instantly, I cant see any evidence of greylisting in operation, nothing in the logs about blocking the initial message.

[root@mail ~]# grep smtpd_recipient_restrictions /etc/postfix/main.cf

through Postfix. See the smtpd_recipient_restrictions parameter relay mail to. See the smtpd_recipient_restrictions description in

smtpd_recipient_restrictions = permit_mynetworks, permit_inet_interfaces, permit_sasl_authenticated, reject_unauth_pipelining, reject_unknown_recipient_domain, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, permit check_policy_service unix:/var/spool/postfix/postgrey/socket

Wed, 01/23/2019 - 11:19
amityweb

fixed it...

in /etc/postfix/main.cf, "permit" must come at the end of the smtpd_recipient_restrictions line.

I have manually created or modified this, so I guess the automated install just added the check_policy_service on the end of that line and does not check where permit is.

So moving permit to the end and its working now: smtpd_recipient_restrictions = permit_mynetworks, permit_inet_interfaces, permit_sasl_authenticated, reject_unauth_pipelining, reject_unknown_recipient_domain, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, check_policy_service unix:/var/spool/postfix/postgrey/socket, permit

Although I dont think its whitelisting a successful user, every email from a user seems to be blocked, I thought it was the first email only, maybe I am wrong.

Sat, 01/26/2019 - 12:25
KAtwitch

I can confirm that this worked for me as well. I did not change any settings, I just moved the line that starts with "smtpd_recipient_restrictions..." to the end of the file. After that, I was able to install the postgrey user and service with the GUI.

Thanks for your persistence with this! It helped me out.

Mon, 01/28/2019 - 03:44
amityweb

I have had to disable it now. Although during my tests (which included from a Yahoo email), one of my customers was receiving no email from his customers or from his own Yahoo email. He waited far beyond the 5 minutes greylisting waits. As soon as I disabled Greylisting all his emails started to arrive. So I am quite disappointed its not working fully.

I enabled it because I think spamassassin is rubbish and I am getting load of these similar spam emails the past week, but greylisting did not stop them anyway!

Topic locked