Facebook
Twitter-
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.
Question XML API - get option value for "do not deliver copies of forwarded emails to mailbox"
- Thread starter mela
- Start date
The delivery option for forwarding isn't available on the XML API.
However it is available for usage with the CLI, which you can run via the REST API with the CLI method.
As a side note: Unfortunately the
Hope this helps.
However it is available for usage with the CLI, which you can run via the REST API with the CLI method.
Code:
plesk bin mail -u <[email protected]> -forwarding true -delivery falseAs a side note: Unfortunately the
-delivery option for the mail utility (still) isn't listed on the CLI documentation page (3 years after it got introduced). But it got mentioned on the Change Log for Plesk for the 18.0.42 release.Hope this helps.
Last edited:
Thank you for the feedback, I have created an internal request to the docs.team to update the documentation page.