Facebook
TwitterMy suggestion, make the limits have an option to behave like they did in Plesk 8.x, 7.x and probably earlier. In those versions, traffic and disk usage were allowed to exceed the limit if you chose to allow it but email accounts, databases, etc. were not allowed to go over the set limits. In 9.x, if you allow over usage at all, it allows over usage of everything and then sends customers confusing notification emails about being over their plan even though the email doesn't include what they're actually over on since they only include disk and traffic. We bill for going over on traffic and disk and do not want to allow customers to go over on email accounts, etc.; we can no longer prevent that since we can't shut sites off when they hit their traffic limit obviously.
-
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.
Allow limits to behave like they used to...
- Thread starter HostaHost
- Start date
