• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Problem with greylisting

mow

Silver Pleskian
Server operating system version
Debian 11.5 x86_64
Plesk version and microupdate number
Plesk Obsidian 18.0.44.3
Hi,

greylisting seems too strict:

Code:
Nov  1 04:07:22 sourcetronic postfix/smtpd[1757448]: connect from server1
Nov  1 04:07:24 sourcetronic postfix/smtpd[1757448]: 31CA612A2AA2: client=server1
Nov  1 04:07:24 sourcetronic psa-pc-remote[5133]: 31CA612A2AA2: from=…
Nov  1 04:07:24 sourcetronic psa-pc-remote[5133]: 31CA612A2AA2: grey: stderr: SKIP
Nov  1 04:07:24 sourcetronic psa-pc-remote[5133]: 31CA612A2AA2: grey: stderr: SKIP
Nov  1 04:07:24 sourcetronic psa-pc-remote[5133]: 31CA612A2AA2: grey: stderr: DEFER
Nov  1 04:07:24 sourcetronic psa-pc-remote[5133]: Message aborted.

Nov  1 04:07:28 sourcetronic postfix/smtpd[1757448]: connect from server2
Nov  1 04:07:29 sourcetronic postfix/smtpd[1757448]: 38C3B12A2AA2: client=server2
Nov  1 04:07:29 sourcetronic psa-pc-remote[5133]: 38C3B12A2AA2: from=…
Nov  1 04:07:29 sourcetronic psa-pc-remote[5133]: 38C3B12A2AA2: grey: stderr: DEFER
Nov  1 04:07:29 sourcetronic psa-pc-remote[5133]: Message aborted.

Nov  1 04:15:06 sourcetronic postfix/smtpd[1757644]: connect from server2
Nov  1 04:15:07 sourcetronic postfix/smtpd[1757644]: CD34712A2AA2: client=server2
Nov  1 04:15:07 sourcetronic psa-pc-remote[5133]: CD34712A2AA2: from=…
Nov  1 04:15:07 sourcetronic psa-pc-remote[5133]: CD34712A2AA2: grey: stderr: SKIP
Nov  1 04:15:07 sourcetronic psa-pc-remote[5133]: CD34712A2AA2: grey: stderr: DEFER
Nov  1 04:15:07 sourcetronic psa-pc-remote[5133]: Message aborted.

Nov  1 04:25:06 sourcetronic postfix/smtpd[1757829]: connect from server2
Nov  1 04:25:07 sourcetronic postfix/smtpd[1757829]: EA6E912A2AA2: client=server2
Nov  1 04:25:07 sourcetronic psa-pc-remote[5133]: EA6E912A2AA2: from=…
Nov  1 04:25:07 sourcetronic psa-pc-remote[5133]: EA6E912A2AA2: grey: stderr: SKIP
Nov  1 04:25:07 sourcetronic psa-pc-remote[5133]: EA6E912A2AA2: grey: stderr: SKIP
Nov  1 04:25:08 sourcetronic psa-pc-remote[5133]: EA6E912A2AA2: grey: stderr: DEFER
Nov  1 04:25:08 sourcetronic psa-pc-remote[5133]: Message aborted.
(tl;dr: sending provider connects first from one IP, then three times from another, then the sender gives up)

What is interesting: On the first attempt, grey results in SKIP, SKIP, DEFER, on the next attempt with the other IP it immediately goes to DEFER, then SKIP, DEFER, then SKIP, SKIP, DEFER, and I'd guess the next attempt, if it came, would be SKIP, SKIP, SKIP and go through.

Now, why would Plesk do that? What is the meaning of the first and second check? (I guess the third is the connection database check recognizing the previous attempt.)
Penalty for reconnecting too fast is supposed to be switched off, and could only be valid for the second attempt anyway, but not the third or fourth:
Penalty interval 2 minutes Penalty disabled
 
Back
Top