• 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.

Recent content by bago

  1. B

    Resolved Google to soon require ARC for forwarded messages

    Is there an ETA? it's less than 90 days before Google will start rejecting our emails: we have to know when we can configure and test things, otherwise we have to move away from Plesk... This should be very high priority but I can't find anything around but this post :-(
  2. B

    Resolved Bug with XMLApi call to add/remove forwarding ("Unable to activate or deactivate mail group: You should add a mail group member before...")

    I identified a workaround for the API workflow by removing the address field from the disable call: so: instead of Sounds like this way a following call to enable the redirect will work fine.
  3. B

    Resolved Bug with XMLApi call to add/remove forwarding ("Unable to activate or deactivate mail group: You should add a mail group member before...")

    Unfortunately the workaround doesn't work for me as the API user is an external application. I would need an API based workaround. Is it about some weird DB status? I could try running some update query in the cron to attempt to prevent the issue, in this case (I know I can investigate this on...
  4. B

    Resolved Bug with XMLApi call to add/remove forwarding ("Unable to activate or deactivate mail group: You should add a mail group member before...")

    Sure! I didn't use that format because I was not in the report section, yet ;-) PRODUCT/VERSION, OS/ARCHITECTURE OS version, architecture: CentOS Linux 7.9.2009 (Core) Product version (including MU): Plesk Obsidian v18.0.50_build1800230213.12 os_CentOS 7 PROBLEM DESCRIPTION Receive an API...
  5. B

    Resolved Bug with XMLApi call to add/remove forwarding ("Unable to activate or deactivate mail group: You should add a mail group member before...")

    This sequence always reproduce the issue: Enable forwarding Disable forwarding Try to enable again forwarding fails: ERROR: SAME CALL AGAIN works: WORKS:
  6. B

    Resolved Bug with XMLApi call to add/remove forwarding ("Unable to activate or deactivate mail group: You should add a mail group member before...")

    Hi, I have a weird issue with XMLApi usage to remotely add/remove email forwarding to users. I just created my forum account in order to report the issue but I can't post to the report forum, so here I am. The fact is that a call to enable forwarding sometimes ends up doing the opposite thing...
Back
Top