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

Resolved Mailbox Usage Notification Only Sent in English Despite Custom Text in Settings

TorbHo

Regular Pleskian
Server operating system version
Debian 11.11
Plesk version and microupdate number
Plesk Obsidian 18.0.67 Update 2
We've noticed that the automatic email "Mailbox usage exceeded 95% of quota limits" is now only being sent to our customers in English. This happens even though we have set up our own custom text under "Settings -> Mail settings".

Has anyone else experienced this issue? Is there a known fix or workaround to ensure that our custom message is used instead of the default English text?

Any insights would be greatly appreciated!

Thanks in advance!
 
Thank you for your reply.

This file contains the correct version in German. However, it might have been overwritten when we saved the message again for diagnostic purposes, as it has a recent timestamp.

Could the file have been overwritten by a previous update, causing the standard message to be used temporarily?

We can only continue testing once a customer's mailbox is nearly full again. Or is there another way?
 
The file shouldn't be overwritten. The session might have been interrupted while saving the changes in the GUI, which could have resulted in the file not being properly updated in the first place. For testing purposes what I can suggest is creating a new service plan and setting the mailbox quota low, e.g. ~10 KB, you can then assign the service plan to a new test subscription. It should be fairly easy to reach a mailbox size of 10KB and test the notification. I hope that helps.
 
With your tip, I was able to test it. It seems to be working now, but the cause remains unclear.

Can I also set the quota from 95% to, for example, 80%?
 
Back
Top