• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • 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.

Why is postfix accepting and bouncing over quota accounts instead of rejecting?

HostaHost

Regular Pleskian
Postfix with Plesk 11 appears to accept messages for accounts, even if they're over their quota, and then generates a bounce back; as opposed to simply rejecting the message to begin with. This is causing blacklisting issues. What config needs to be changed to prevent this?

This is the mail system at host X.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

The mail system

<user@domain>: Mail quota exceeded
 
I had time to look through this today. I think you misunderstood what I'm seeing happen. On our Plesk 11 Postfix servers, messages to accounts that are over quota are being accepted from the remote SMTP sending server, then a bounce message sent back to that sender (or to an innocent victim in the case of a forged sender on a spam message).

In http://kb.parallels.com/115395, it sounds like our servers are not behaving as expected. The article makes it sound like what should be happening when an account is over quota is that the incoming SMTP attempt from the sending server should be responded to with a 4.x.x status rejection and the message refused for the sender to try again later. The article then goes on to tell you how to update that response to a 5.x.x permanent rejection instead. In our case, I'm not seeing the servers issue a 4.x.x rejection to begin with, they accept the message and then generate an outbound bounce message from mailer-daemon with the contents I quoted in the first post.
 
Back
Top