• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Plesk Email Security: Unable to disable greylisting server-wide, per-mailname, per-domain

maltris

New Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
18.0.77 Update #2
Hello community,

I am trying to disable graylisting for various domainnames or mailnames. With the cli tool I was able to alter the status of the greylisting, but it appears to me that using the Plesk Email Security extension, these statuses dont really matter. The mail appliance keeps greylisting and also explicitly states that in the logs, which is very unfortunate.

Actually I tried to research using the available documentation, but it does not appear to yield any results. The main recommendation is to use the cli tool.


Bash:
# plesk bin grey_listing --info-server
Grey listing configuration.

Grey listing checking  disabled

Bash:
# plesk bin grey_listing -id domain.com
Grey listing for domain is disabled
SUCCESS:  Gathering information for 'domain.com' complete.

Bash:
# plesk bin grey_listing -im "[email protected]"
Grey listing configuration for [email protected].

User's black list:

User's white list:

SUCCESS: Gathering information for '[email protected]' complete.

I appreciate any input that leads to solving my issue.

Best regards
 
This issue should be closed. Just figured that I set a custom rspamd instance (via mailcow) via milter protocol in /etc/postfix/main.cf. That instance was greylisting and made the postfix return the greylisting message.
 
Back
Top