Mail Rate Limiting

Submitted by Blueforce on Thu, 02/15/2018 - 19:47 Pro Licensee

Hi,

Mail Rate Limiting in Virtualmin/Email Settings always shows Rate limiting enabled as "No" even if it is enabled. It's the same in both Authentic and Virtualmin Framed theme.

Regards, Leffe

Status: 
Active

Comments

Submitted by JamieCameron on Fri, 02/16/2018 - 23:33

If you change it to "Yes" and click Save, do you get any error message?

Submitted by Blueforce on Sat, 02/17/2018 - 19:03 Pro Licensee

Hi Jamie,

No, there are no error messages! And I know for sure that it is enabled even as it says "No".

//Leffe

Enabling action milter-greylist at boot time ..
.. done

Adjusting socket file ..
.. done

Starting milter-greylist server ..
.. done

Configuring mail server to use milter-greylist server ..
.. done

Updating rate limiting settings ..
.. done

Submitted by JamieCameron on Sun, 02/18/2018 - 17:34

Some things to check :

  • Is the process milter-greylist running on your system?
  • What does grep smtpd_milters /etc/postfix/main.cf output?
  • What does grep smtpd_recipient_restrictions /etc/postfix/main.cf output?
  • Does /etc/init.d/milter-greylist exist?

Submitted by Blueforce on Sun, 02/18/2018 - 21:27 Pro Licensee

The Mail Rate limiting is active and working as it should, the only thing is that it don't show its actual status.

milter-greylist is running.

# grep smtpd_milters /etc/postfix/main.cf
smtpd_milters = local:/var/run/milter-greylist/milter-greylist.sock,inet:localhost:8891
non_smtpd_milters = local:/var/run/milter-greylist/milter-greylist.sock,inet:localhost:8891

# grep smtpd_recipient_restrictions /etc/postfix/main.cf
smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated reject_unauth_destination check_sender_access hash:/etc/postfix/sender_checks reject_rbl_client cbl.abuseat.org reject_rbl_client sbl.spamhaus reject_rbl_client bl.spamcop.net check_policy_service unix:/var/spool/postfix/postgrey/socket

/etc/init.d/milter-greylist exists.

//Leffe

Submitted by JamieCameron on Mon, 02/19/2018 - 23:13

Can you post the full command line of the milter-greylist process, including all command-line args?

Submitted by Blueforce on Tue, 02/20/2018 - 17:51 Pro Licensee

Jamie, I'm not sure what information you want?

Submitted by andreychek on Wed, 02/21/2018 - 10:19

What is the output of this command, this will show that information:

ps auxw | grep milter

Submitted by Blueforce on Wed, 02/21/2018 - 14:27 Pro Licensee

Thanks!

[root@server ~]# ps auxw | grep milter
root     20617  0.0  0.0  11636  1140 ?        S    21:23   0:00 sh -c (ps auxw | grep milter) 2>&1
root     20618  0.0  0.0  11636   576 ?        S    21:23   0:00 sh -c (ps auxw | grep milter) 2>&1
root     20620  0.0  0.0   9044   664 ?        S    21:23   0:00 grep milter
grmilter 29310  0.0  0.0 403636  7328 ?        Ssl  00:28   0:05 /usr/sbin/milter-greylist -u grmilter -P /var/run/milter-greylist.pid

[root@server ~]#

Submitted by webwzrd on Mon, 07/16/2018 - 17:02 Pro Licensee

Did this ever get resolved? I've had the same issue too for quite some time now.

Submitted by Blueforce on Mon, 07/16/2018 - 17:22 Pro Licensee

I actually dont know, I have not changed anything on the mail rate limiting for some time now. But I guess this has not been fixed since issue still is active

//Leffe

Submitted by b1cata on Wed, 12/12/2018 - 16:19

In /etc/mail/greylist.conf change the line: socket "/run/milter-greylist/milter-greylist.sock" 666
into: socket "/var/milter-greylist/milter-greylist.sock" 666

Virtualmin seems to check existence of the socket in another location.

Regards,
Catalin