• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Qmail configuration - please do not touch

L

Lorenz-IT

Guest
Our server acts as secondary mail server for several domains and after each Plesk update I have to configure it another time, because Parallels means to write the default configuration is sensful as often as possible.

I would be the luckiest Plesk user, if Parallels would leave my servers qmail konfiguration untouched with their updates.

Thanks ahead!
 
We have KB article about Qmail patching http://kb.odin.com/en/1161 but I'm not sure that we should expect any customer's qmail customizations and do not overwrite it with Plesk update.
 
We have KB article about Qmail patching http://kb.odin.com/en/1161 but I'm not sure that we should expect any customer's qmail customizations and do not overwrite it with Plesk update.

I agree, that you cannot consider each posssible customized configuration. But what is the idea behind rewriting the rcpthosts, the smtproutes or the locals configuration each time an update of the binaries takes place?
In my humble opinion, this makes absolute no sense, but ends in problems for each customer, which has to personalize this files.
 
Back
Top