• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  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...
    • bago
    • Thread
    • bug bug api xml api
    • Replies: 10
    • Forum: Reports
Back
Top