• 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.

Resolved Plesk Update 18.0.80 mail queue manager is far less useful

MHC_1

Regular Pleskian
Server operating system version
Alma Linux 9.8
Plesk version and microupdate number
Obsidian 18.0.80
Since 18.0.80 (absolutely sure it is since this update) The Mail Queue manager GUI appears to no longer state reasons why a mail is held , and also the GUI is unable (there's no button) to reset or try and repost mails, which there used to be,

There is only 1 "link" on each mail and that simply shows the Mail header data but doesn't show what was previously available which was a feedback text as to why the mail was being held / undelivered.

Please can this be reverted or otherwise explained?

We use Amavisd and Postfix

Thank you.
 
Hi, @MHC_1 . I can't seem to be able to replicate the behavior on a test environment with Plesk Obsidian 18.0.8 #5. What I noticed, however, is that the was some delay before the reason was displayed. Can you please try refreshing the queue and confirm if the issue still persists for older entries? Thanks in advance.
 

Attachments

  • Screenshot 2026-09-01 113007.png
    Screenshot 2026-09-01 113007.png
    190.8 KB · Views: 13
Hi, @MHC_1 . I can't seem to be able to replicate the behavior on a test environment with Plesk Obsidian 18.0.8 #5. What I noticed, however, is that the was some delay before the reason was displayed. Can you please try refreshing the queue and confirm if the issue still persists for older entries? Thanks in advance.
Hello
Sorry for the delay replying. We had regularly refreshed the queue and reviewed it several times over the day before posting here.

In the end the Amavisd and Postfix services were manually restarted as per this post: https://support.plesk.com/hc/en-us/...t-while-receiving-the-initial-server-greeting which resolved the issue.
 
Back
Top