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

Issue Mailbox full on an unlimited

Yannick Croteau

New Pleskian
We have 2 Onyx servers. And we have the same problem with both of them.

We are under

Onyx 17.0
CentOS 7.2,
postfix
Horde
Plesk Courier

The whole domain can't receive mails, because the system see all mailboxs full, but the subscription is set as unlimited.

At this time we had the problem only with transfered site from plesk 11.5 and 12.5 . We didn't try with domains started on Onyx.

The problem may appear after a "plesk repair mail domain.com", even if all is OK and the repair fix nothing.

For fix it (temporarily), we put a limite (like 5Gb) and we put back the unlimite again and it's working for a while. But the problem can come back at any time.

There some log exemples

Mar 23 09:09:45 server1 postfix/cleanup[14925]: 24530832C5: milter-reject: END-OF-MESSAGE from ....: 4.2.2 Mailbox full; from=<...> to=<...> proto=ESMTP helo=<....>
Mar 23 09:10:28 server1 /usr/lib64/plesk-9.0/psa-pc-remote[11837]: handlers_stderr: DATA REPLY:452:4.2.2 Mailbox full#012DEFER
Mar 23 09:10:28 server1 postfix/cleanup[14925]: 900A8832CC: milter-reject: END-OF-MESSAGE from mx1.b2b2c.ca[66.158.128.35]: 4.2.2 Mailbox full; from=<> to=<> proto=ESMTP helo=<....>
Mar 23 09:10:29 server1/usr/lib64/plesk-9.0/psa-pc-remote[11837]: handlers_stderr: DATA REPLY:452:4.2.2 Mailbox full#012DEFER
Mar 23 09:10:29 server1 postfix/cleanup[17351]: 741C1832CC: milter-reject: END-OF-MESSAGE from ....: 4.2.2 Mailbox full; from=<....> to=<....> proto=ESMTP helo=<JohnP>
Mar 23 09:10:32 server1 /usr/lib64/plesk-9.0/psa-pc-remote[11837]: handlers_stderr: DATA REPLY:452:4.2.2 Mailbox full#012DEFER
Mar 23 09:10:32 server1 postfix/cleanup[14925]: 1210B832D6: milter-reject: END-OF-MESSAGE from ....: 4.2.2 Mailbox full; from=<....> to=<....> proto=ESMTP helo=<....>



Thank you for helping!

Yannick
 
Last edited:
I would suggest you contact Plesk Support Team. It will be quicker and you will get a fix for your server. Or you can submit report here Reports and I will forward it to developers for investigation. But it will take more time.
 
I have seen this as well from time to time on some rare occasions in the past.....

EDIT: read it again.... Not true what I wrote... These domains of mine did have a limit, but they were "soft limits" . The problem was that they were handled "in a hard way".
 
Hi,
I have the same error. But I don't see any limits reached in Plesk (just 6% usage of space (hardquota), mailboxsize 120M from unlimited).
But sometimes I get:
<date> <server> /usr/lib64/plesk-9.0/psa-pc-remote[6109]: handlers_stderr: DATA REPLY:452:4.2.2 Mailbox full#012DEFER
<date> <server> /usr/lib64/plesk-9.0/psa-pc-remote[6109]: DEFER during call 'check-quota' handler


Do you have any idea where this can come from?
is there a list somewhere which settings all can cause this error?
 
Back
Top