• 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!
  • 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.

Search results

  1. J

    Resolved shrinker.py: no such file or directory

    Yes, it worked for me, no more e-mails received.
  2. J

    Resolved shrinker.py: no such file or directory

    Finally (the second time I tried), the article https://support.plesk.com/hc/en-us/articles/360012999480-Email-notifications-are-received-daily-from-a-Plesk-server-etc-cron-daily-imunify360-firewall-exited-with-return-code-127 helped me out, with the following command: on Debian/Ubuntu-based...
  3. J

    Resolved shrinker.py: no such file or directory

    Hello Igor, thank you. It helped me to remove the existing cronjobs from Imunify, and the error messages about those cronjobs by e-mail since I deleted Imunify from Plesk. The only message I keep receiving is: /usr/bin/flock -n /var/run/shrinker.lock /opt/alt/python38/bin/python3...
Back
Top