From 10.4.4 release notes:
[+] (Only for Linux) Mailboxes do not accept new mail if the mailbox quota is exceeded. Both Qmail and Postfix will reject incoming mail when the target mailbox is over quota instead of bouncing it as before. The previous behavior was known as backscattering and might have caused Plesk server getting in antispam DNS blacklists.
This new feature is broke for several reasons:
1) It completely changes the functionality of mail handling on the server.
2) It's not optional and is enabled by default.
3) You don't have the choice of selecting a 5xx or 4xx response if a customer's mailbox is full.
4) The server responds with "Command rejected" after DATA, not something useful like "Mailbox full".
Jan 9 21:48:13 plesk postfix/cleanup[26095]: A40DD600A71: milter-reject: END-OF-MESSAGE from [70.99.x.x]: 5.7.1 Command rejected; from=<> to=<> proto=ESMTP helo=<>
This either needs to be made configurable in the GUI or you need to tell us how to disable it via CLI because how it is now is broke.
Thank you.
[+] (Only for Linux) Mailboxes do not accept new mail if the mailbox quota is exceeded. Both Qmail and Postfix will reject incoming mail when the target mailbox is over quota instead of bouncing it as before. The previous behavior was known as backscattering and might have caused Plesk server getting in antispam DNS blacklists.
This new feature is broke for several reasons:
1) It completely changes the functionality of mail handling on the server.
2) It's not optional and is enabled by default.
3) You don't have the choice of selecting a 5xx or 4xx response if a customer's mailbox is full.
4) The server responds with "Command rejected" after DATA, not something useful like "Mailbox full".
Jan 9 21:48:13 plesk postfix/cleanup[26095]: A40DD600A71: milter-reject: END-OF-MESSAGE from [70.99.x.x]: 5.7.1 Command rejected; from=<> to=<> proto=ESMTP helo=<>
This either needs to be made configurable in the GUI or you need to tell us how to disable it via CLI because how it is now is broke.
Thank you.