• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved SMTP-Server (Postfix) stops when changing subscriber.

Michael Steinle

New Pleskian
Now happend a second time:
After changing the subscriber of a subscription, the service "SMTP-Server (Postfix)" stopped.

Is this a known bug?

(I hope, "subscription" is the correct word for the "Abonnement" in the german Version of Plesk.)

...

Additional:
When I have a subscription with only an IPv4 and want to add an IPv6, I have to change the subscriber.
Is there a better, direct way to add an IPv6 to a subscription?
 
When I have a subscription with only an IPv4 and want to add an IPv6, I have to change the subscriber.
Is there a better, direct way to add an IPv6 to a subscription?
Click on the "web hosting access" icon, then select the IPv6 address from the drop down box and confirm the change with "OK".

webhosting_access.jpg
 
Thank you very much !!!

I must have been blind ...
As this setting is for the complete subscription, I probably didn't search at the level where settings for a single domain are made.
 
After changing the subscriber of a subscription, the service "SMTP-Server (Postfix)" stopped.
- In /var/log/maillog and /var/log/messages: Do you see any interesting log entries that refer to Postfix for the time when the service stops?
- When you run
# service postfix status
when it is down, what exactly is displayed?
 
Thanks for your continued help.
I am not the server-admin, so your questions are complex for me.

Meanwhile we tried to reproduce the bug, what didnt't work.

My server-admin saw in the log many attacks as reason to stop the service.

Strange temporal correlation ... but I will accept this ... and will have an intensive look on the SMTP-Server after working in plesk.
 
Back
Top