Recent content by bago

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 :-(

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.

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

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

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

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