• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Forwarders created with API do not work

P

pstephan1187

Guest
When I create a forwarder with the API, the forwarder gets created. I can see it in plesk and the API will return the forwarder when I ask for it as well. The problem is that when I send an email to the original address, the email will not get forwarded. For example, if I create an email account [email protected] and set it to forward to [email protected] with the API and then send an email to [email protected], the email will be received by "test" but not "me". Plesk will verify that [email protected] is set as a forwarder for [email protected].

If I duplicate the process, but instead created the account and set the forwarder via plesk instead of the API, then the forwarder receives the email.

Does anyone know how to fix this?
 
Back
Top