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

Question Email forwarding with SES

janewi

New Pleskian
Hi everyone!

Postfix on our server is configured to send outgoing emails via Amazon SES. However, when forwarding emails for an email address of a domain hosted on the Plesk server to an email address not hosted on our servers, SES will refuse to deliver the email as the sender cannot be authorized. While this behaviour is technically correct (the sender address is not a domain managed by the server so the message shouldn't allowed to be sent), it prevents me from using the forwarding feature in Plesk with external domains.

To work around this, I was thinking about...
  • ... using a different SMTP relay for sending when forwarding (possibly even just sending it directly from the local server if that is possible), or
  • ... rewriting the email headers when forwarding somehow
Do any of you other suggestion on how to work around this? How could I implement any of it?

Thanks a lot in advance!
 
Hi everyone!

Postfix on our server is configured to send outgoing emails via Amazon SES. However, when forwarding emails for an email address of a domain hosted on the Plesk server to an email address not hosted on our servers, SES will refuse to deliver the email as the sender cannot be authorized. While this behaviour is technically correct (the sender address is not a domain managed by the server so the message shouldn't allowed to be sent), it prevents me from using the forwarding feature in Plesk with external domains.

To work around this, I was thinking about...
  • ... using a different SMTP relay for sending when forwarding (possibly even just sending it directly from the local server if that is possible), or
  • ... rewriting the email headers when forwarding somehow
Do any of you other suggestion on how to work around this? How could I implement any of it?

Thanks a lot in advance!
Have you solved it yet? I am also having a similar problem. Please share the solution. Thanks.
 
Back
Top