Search results

The same was happening for me for a domain which already had DKIM active, but had no DKIM keypair yet. After I first turned of DKIM signing and then turned it back on via the CLI, a default DKIM key was generated and the UI now shows an active selector (default) and the "How to configure...

I am not sure if this is part of the issue, but so far I haven't been able to find a CLI equivalent for generating a DKIM keypair. It would be nice (read: required) to have this option, as simply disabling/enabling does not suffice.

Ok, now that 18.0.45 update 1 is installed, we also get the following error: 554 5.7.1 <[email protected]>: Relay access denied Adding 127.0.0.0/8 to the whitelist solves this indeed, but IMHO this should have been handled by the update.

To work around this issue, one can temporarily use: Swift mailer: Symfony mailer: But lets hope for a timely fix from the Plesk devs as this alternative method is not recommended.

Well, that's not very... helpful. :-)

I can confirm the same issue with the older and unsupported Swiftmailer, as well as the newer Symfony mailer.

I tried this already, but unfortunately:

Hi, As of Plesk Obsidian 18.0.44 (24 may 2022), and more specifically PPPM-13497 the -bs options appears to be disallowed from the postfix-sendmail-wrapper. I take it this is the "fix" for being able to bypass email sending restrictions? Since this update we encounter the following issues on...

Apparently it's solved, thanks!

When upgrading Plesk Onyx 17.8 to Obsidian 18.0.23 in CentOS 7, the upgrade fails partially when updating extensions. The issue seems global though, not related to plesk/OS version. Afterwards, I'm unable to access the extensions catalog. The installation log shows: Rerunning the failed...