• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Qmail gives 451 temp error when mailbox full

According to RFC 1893, section "3.3 Mailbox status" Mail box full should be temporary error, but Plesk returns permanent error. With applied fix from MU#27, when mailbox is full the following error is returned:
"5.7.1 Mailbox full"

According to RFC 1893:

================================

X.2.2 Mailbox full

The mailbox is full because the user has exceeded a
per-mailbox administrative quota or physical capacity. The
general semantics implies that the recipient can delete
messages to make more space available. This code should be
used as a persistent transient failure.

================================

4.X.X Persistent Transient Failure

A persistent transient failure is one in which the message as
sent is valid, but some temporary event prevents the successful
sending of the message. Sending in the future may be successful.

================================

So, it means that instead of
"571 5.7.1 Mailbox full"
the error message should be returned:
"450 4.2.2 Mailbox full"

But now it returns 421 instead of 422. It will be fixed in 11.1
 
Plesk 11? seriously?
So screw everyone on plesk 10?

Hello Cpanel Migration Team,

Here we are again. Thanks again for your kind reply a few weeks ago!
We are definitely going ahead with the free migration of our 23 plesk servers.
(...)
 
This is not done. What is the option for those who are still on 10 and waiting for your update?
Is there any workaround? The one suggested earlier is not working at all.
 
Plesk 10 ?? Whats the fix for that?
After using Plesk 10 and repeated issues like this I have no confidence to move to Plesk 11 even.

Please let us know if there is any relief for Plesk 10 users or not?
 
I just want to say that upgrade to Plesk 11 – is more like a 10.5 upgrade than a full version upgrade.
 
According to developers this issue was completely fixed in Plesk 11.0.9
 
Back
Top