• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Postfix Error or Plesk Repair Error?

G J Piper

Regular Pleskian
TITLE:
Postfix Error or Plesk Repair Error?
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
CentOS 6.8, Plesk Onyx 17.0.17r21
PROBLEM DESCRIPTION:
When restarting postfix, this warning shows up in the error logs about incorrect permissions:
postfix/postfix-script[7780]: warning: not set-gid or not owner+group+world executable: /usr/sbin/postdrop

The postfix warning is fixed by running "postfix set-permissions"

When running the "plesk repair" utility afterward, it gives this message:
Reconfiguring the Plesk installation
Checking the Plesk database using the native database server tools .. [OK]
Checking the structure of the Plesk database ........................ [OK]
Checking the consistency of the Plesk database ...................... [OK]
Checking system users ............................................... [OK]
Checking Linux system files
There are incorrect permissions on some items: /usr/sbin/postdrop . [ERROR]
To see more details, run the command in the verbose mode: plesk repair fs -verbose
Checking virtual hosts' file system ................................. [OK]
Repairing web server configuration .................................. [OK]
Checking the usage of PHP handlers .................................. [OK]
Repairing the mail server configuration ............................. [OK]
Checking the DNS configuration file ................................. [OK]
Restoring DNS server configuration .................................. [OK]
Checking MySQL database servers ..................................... [OK]
Repair databases on available servers ............................... [OK]
Repair database users on available servers .......................... [OK]
Error messages: 1; Warnings: 0; Errors resolved: 0​
STEPS TO REPRODUCE:
Fix Postfix log warnings with "postfix set-permissions"​
ACTUAL RESULT:
Plesk repair utility throws it's own error.​
EXPECTED RESULT:
no error warnings when everything seems to be running fine​
ANY ADDITIONAL INFORMATION:
Fixing the error in Plesk Repair Utility causes the posfix error to resurface.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Confirm bug
 
Unconfirmed:

This is expected behaviour.
Permissions to /usr/sbin/postdrop are changed by Plesk in order to implement Outgoing Antispam Protection.
If you set default permissions to postdrop as Postfix suggests then any user with shell access will be able to send emails using postdrop without being restricted by Plesk outgoing antispam.
On the other side, we are shipping postfix package by OS vendor and do not patch/rebuild it somehow, so we cannot get rid of this warning in logs.
So, permissions suggested by "plesk repair fs" are correct.
 
Back
Top