Forwarded to devs [PPP-47160][Plesk 18.0.23 on CentOS 7] Internal error on Server-Wide Mail Settings page

[Monty]

Still have a few confusion about changelog page Change Log for Plesk Obsidian

Yah changelog was not yet updated. The update was only released about 1.5h ago, so I guess we'll see an updated changelog some time during the day

 

[Bitpalast]

I have had the same error today, however on a second attempt the page suddenly worked.

 

[sebgonzes]

I have had the same error today, however on a second attempt the page suddenly worked.

Go it again then after enable the mail setting, yesterday almost, error appear again.

 

[Werner99]

ok first issue fixed but i have another one now with DKIM and DMARC anyway will open a new report

 

[moswak]

The microupdate 18.0.23 update # 1 is also buggy

- there is no longer a possibility to enter a blacklist. the previously entered blacklists (spamcop etc.) disappear from main.cf as soon as saved the settingspage.
- Outgoing mail mode has no IP defined
- The anti-virus filter used is not set to any

 

[learning_curve]

The microupdate 18.0.23 update # 1 is also buggy
- there is no longer a possibility to enter a blacklist. the previously entered blacklists (spamcop etc.) disappear from main.cf as soon as saved the settingspage. - Outgoing mail mode has no IP defined - The anti-virus filter used is not set to any

There appears to be very little incentive to run this microupdate then
Unless, it's run out of peak hours and only after taking a full server snapshot before runing it, so that there's a full recovery position, back to 18.0.23 GA (with no updates....) just in-case these new bugs, only apply to some Plesk / OS setups & not all of them? Other posts may confirm << this soon.

 

[moswak]

to some Plesk / OS setups & not all of them?

with us centos 6 an 7

this is definitely the point where we will deactivate the automatic updates on all obsidian servers until further notice. the servers remain at 18.0.21
very unfortunate that updates come and damage the basic functions like the mail configuration if customer save the mailsettingspage.

 

[Brujo]

based on the changelog I realy wonder if this microupdate will fix the issue here, because it refers to servers without installed DNS server

Plesk Obsidian 18.0.23 Update 1
On Plesk servers without an installed DNS server, updating to Plesk Obsidian 18.0.23 no longer results in an internal error when trying to access mail setting. (PPPM-11478)

 

[moswak]

the problem number 1 "calling the mail server settings and server errors" was solved by the microupdate. the other mistakes do not.
only helps nothing if the mail server settings are partly default or values are missing or cannot be reset.
we can only wait

 

[learning_curve]

We've never used Auto Updates on either Plesk Onyx or Plesk Obsidian. We've always run them manually (for controlled recovery purposes).

Moving back to this issue, we've sucessfully run #Update 1 exactly as outlined in our post #26 above. We have no faults & no new bugs. The same result as when we upgraded to 18.0.23 GA initailly. As a result, there was no need for us to recover back to 18.0.23 GA using our server snapshot.

However, as mentioned in post #17, we have no current requirements to make any further changes in this 'affected' area, thus may not be 'seeing' the issue like everyone else is. No, we're not going to make some changes, just to see if we can cause an issue We'll wait for Plesk to respond!

 

[Alexey Sinko]

any update, when can we expect a fix?

Plesk 18.0.23.2 was released, it will solve your problem.