Facebook
TwitterPostfix 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?
-
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.
Why is postfix accepting and bouncing over quota accounts instead of rejecting?
- Thread starter HostaHost
- Start date
Look at this article - http://kb.parallels.com/115395
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.
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.
Similar threads
