Issue Plesk Notifications are not being sent

[Fede Marsell]

Server operating system version

AlmaLinux 8

Plesk version and microupdate number

Plesk Obsidian 18.0.68 Update 2

Hello,

After the latest update to Plesk Obsidian 18.0.68 Update 2, Plesk has stopped sending limit exceeded warnings.

This has happened on 14 servers. On all of them, after updating to the latest version, Plesk Obsidian 18.0.68 Update 2.

In all cases, the operating system is AlmaLinux 8.

Any idea what could be happening? I understand that since it happened on multiple servers, it must be something related to Plesk. But I don't see any notifications about any bugs or similar.

The statistics are being calculated correctly. I manually ran the statistics on a domain with exceeded limits, and Plesk marks it as overuse but doesn't send any emails.

Any help would be appreciated

 

[Sebahat.hadzhi]

Hello, @Fede Marsell . Do you by any chance have addons for additional disk space? If not, please provide us with the current configuration of the subscription in question and the Notifications settings, please.

 

[Fede Marsell]

Hello, @Sebahat.hadzhi

No, I don't have any extensions. As I mentioned, the problem occurred on several servers at once. The only thing I did was upgrade to Plesk Obsidian 18.0.68 Update 2.

If you tell me what you need, I can provide the details, of course.

 

[Sebahat.hadzhi]

Thanks for the confirmation. Could you please confirm the following:

1. Is Plesk configured with local or remote SMTP?
2. If the email addresses the notification is supposed to be sent to are local addresses, please confirm the status of the mail service for the domain name
3. What is the current configuration in Tools & Settings > Notifications for these particular notifications

 

[Fede Marsell]

Thanks for the confirmation. Could you please confirm the following:

1. Is Plesk configured with local or remote SMTP?
2. If the email addresses the notification is supposed to be sent to are local addresses, please confirm the status of the mail service for the domain name
3. What is the current configuration in Tools & Settings > Notifications for these particular notifications

Thank you for your response.

1. Plesk is configured as local.
2. The addresses to which the overuse notifications are sent are either local or remote (e.g., Gmail, Hotmail, etc.). I've checked the maillog, and Plesk is not sending the emails — there's no record of any attempt.

1. I’m attaching two screenshots showing the configuration. They’re in Spanish, but I believe they’re still valid for verification purposes.

On my end, the only change — and what seems to have caused this issue — is the Plesk update.

This has happened on all servers, and I find it odd that no one else is experiencing this issue and it's only affecting me.

Any help is greatly appreciated. I'm not sure if there's something I can run to perform a debug.

 

[Fede Marsell]

The error is related to laminas-mail. This component was updated in the latest PLESK update.

It seems to have problems with the administrator name (it includes a hyphen and a comma). Incredible. Who developed this?

I've changed the name in PLESK, and tomorrow I'll check if the emails are being sent correctly.

[2025-04-03 03:51:25.329] 2617108:67ede99ceb2e0 ERR [panel] 'Admin - Name' can not be matched against dot-atom format:
0: /usr/local/psa/admin/plib/vendor/plesk/laminas-mail/src/Address.php:83

 

[Sebahat.hadzhi]

Yes, you are correct. laminas-mail was updated prior to the latest release and it appears that the validation mechanism was also adjusted. As far as I can see, the end goals is compliance with RFC 5322. It appears that, if special character is followed by a space, or even a blank space it could cause issue. If necessary to have the admin configured as 'Admin - Name' let me know, so I can attempt to find a workaround.

 

[Fede Marsell]

I’ve changed the name on all the servers. Problem solved.

To be honest, it seems like a huge mess. I often wonder what justifies the price of PLESK licenses. These kinds of mistakes are pretty common.

 

[Sebahat.hadzhi]

I am glad to hear you were able to sort out the issue. I just want to mentioned that the validation rules originate from the laminas-mail library, it is not something that Plesk decided to implement. I agree that there is room for improvement on how the value is passed from Plesk, but frankly, I am not entirely sure how many core changes that will involve for such a specific scenario.