• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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