• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

postfix-queue - do we need it?

galaxy

Regular Pleskian
I'm getting ready for the upgrade to 9.0.1 and did a practice install. I noticed postfix is configured to spawn a process for each message coming in and each going out. So the bottleneck here would be the /usr/lib/plesk-9.0/postfix-queue. I've read some problems dealing with large attachments in the program already.

So can the mail system work properly without this? I was already planning on putting in my own hooks for mail handling and would like to avoid spawning processes. I already have my own daemon to process the incoming stream of mail. If there's any important work going on in postfix-queue, I would like to make sure it gets performed, however I can't afford to fork a process for every request.

So does anyone know what postfix-queue does and is it really required? I don't use Dr. Virus, spamassasin or other mail server plugins, but will be using both webmail interfaces.
 
Back
Top