• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Receive Emails with hours of delay - Greylisting

S

Sven76

Guest
System: CentOS 6.2 x64, Plesk 10.4.4

After the last microupdate#23 of Plesk we still habe the problem that e-mails received with hours of delay. In the mail log, we have the following entries.
i replaced the real sender an recipient address with [email protected] (Sender) and [email protected] (recipient)

Here i see, we receive the mail ~3 hours later...


Mar 28 16:36:53 mail postfix/smtpd[25814]: C12752324: milter-reject: DATA from mailserver1.other.de[XXX.XX.XX.XXX]: 451 4.7.1 Service unavailable - try again later; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mailserver1.other.de>
Mar 28 17:07:02 mail postfix/smtpd[27402]: 1061E2324: milter-reject: DATA from mailserver1.other.de[XXX.XX.XX.XXX]: 451 4.7.1 Service unavailable - try again later; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mailserver1.other.de>
Mar 28 17:52:52 mail postfix/smtpd[28630]: 5359A2324: milter-reject: DATA from mailserver1.other.de[XXX.XX.XX.XXX]: 451 4.7.1 Service unavailable - try again later; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mailserver1.other.de>
Mar 28 18:22:54 mail postfix/smtpd[29487]: 2EF842324: milter-reject: DATA from mailserver1.other.de[XXX.XX.XX.XXX]: 451 4.7.1 Service unavailable - try again later; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mailserver1.other.de>
Mar 28 19:22:59 mail postfix/qmgr[7963]: 519A92324: from=<[email protected]>, size=210347, nrcpt=4 (queue active)

------------------
And here one detail entry:
Mar 28 17:07:02 mail postfix/smtpd[27402]: connect from mailserver1.other.de[XXX.XX.XX.XX]
Mar 28 17:07:02 mail postfix/smtpd[27402]: 1061E2324: client=mailserver1.other.de[XXX.XX.XX.XX]
Mar 28 17:07:02 mail greylisting filter[27407]: Starting greylisting filter...
Mar 28 17:07:02 mail greylisting filter[27407]: Timeout finished
Mar 28 17:07:02 mail /usr/lib64/plesk-9.0/psa-pc-remote[29839]: handlers_stderr: SKIP
Mar 28 17:07:02 mail /usr/lib64/plesk-9.0/psa-pc-remote[29839]: SKIP during call 'grey' handler
Mar 28 17:07:02 mail greylisting filter[27408]: Starting greylisting filter...
Mar 28 17:07:02 mail /usr/lib64/plesk-9.0/psa-pc-remote[29839]: handlers_stderr: DEFER
Mar 28 17:07:02 mail /usr/lib64/plesk-9.0/psa-pc-remote[29839]: DEFER during call 'grey' handler
Mar 28 17:07:02 mail /usr/lib64/plesk-9.0/psa-pc-remote[29839]: Message aborted.
Mar 28 17:07:02 mail postfix/smtpd[27402]: 1061E2324: milter-reject: DATA from mailserver1.other.de[XXX.XX.XX.XX]: 451 4.7.1 Service unavailable - try again later; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<mailserver1.other.de>
Mar 28 17:07:02 mail postfix/smtpd[27402]: disconnect from mailserver1.other.de[XXX.XX.XX.XX]

The Greylisting filter reject the first email in "Mar 28 16:36:53", but the next email from the same sender and server is also rejected, why? The 5th try of sending worked...

Here is our greylisting configuration:

/usr/local/psa/bin/grey_listing --info-server

Grey listing configuration.

Grey listing checking enabled
Grey interval 5 minutes
Expire interval 51840 minutes
Penalty interval 2 minutes
Penalty disabled
Personal grey listing
configuration allowed

Server-wide black list:

Server-wide white list:

White domains patterns list:
*google.com
*mail.ru
*parallels.com
*rambler.ru
*yahoo.com
*yandex.ru

Black domains patterns list:
*[0-9][0-9]-[0-9][0-9]-[0-9][0-9]*
*[0-9][0-9].[0-9][0-9].[0-9][0-9]*
*[0-9][0-9][0-9]-[0-9][0-9][0-9]-[0-9][0-9][0-9]*
*[0-9][0-9][0-9].[0-9][0-9][0-9].[0-9[0-9]][0-9]*
dynamic|static|ppp|dyn-ip|dial-up

SUCCESS: Gathering of server wide information complete.

Best regards
Sven
 
Last edited by a moderator:
Hi Helmut,Sven,

What i did to reduce the delay is the following, found this solution on a external forum:
=======from:Quesera

Check /var/qmail/queue/lock/trigger . It should look like this:

stella# ls -l /var/qmail/queue/lock/trigger
prw--w--w- 1 qmails qmail 0 Dec 17 21:56 /var/qmail/queue/lock/trigger

The first character "p" in the `ls -l` output means that the file is a named pipe (also called a "FIFO"). If it's a regular file ("-"), doesn't exist, or if the ownership/permissions are wrong, qmail-send won't get an immediate notification when new messages are added to the queue, and it won't process them until it hits its scheduled wake-up time, typically every 30 minutes.

It's easy to fix:

mkfifo /var/qmail/queue/lock/trigger
chown qmails:qmail /var/qmail/queue/lock/trigger
chmod 622 /var/qmail/queue/lock/trigger

===========

and what i also dis is disabling the Greylist, see: http://kb.parallels.com/6359

If i see your latest post you may fixed it already, but maybe this is useful for others..

Greetings Bryan Hendriquez
 
Back
Top