When using SES, you cannot set FROM header to anything. The FROM has to be either an whitelisted email address or a domain that you own and verified with SES.
When forwarding email, we are receiving email from unknow domains. If we rewrite the FROM headers then the DKIM will invalid, so service will have to rewrite the FROM and clear out DKIM.
```
For example, if an email sent by Jane Example <jane@example.com> to info@example.com is processed by this script, the From and Reply-To headers will be set to:
From: Jane Example at jane@example.com <info@example.com>
Reply-To: jane@example.com
To override this behavior, set a verified fromEmail address (e.g., noreply@example.com) in the config object and the header will look like this.
```
We want to forward email as it is and retain everything so we have to run our own postix in order to do that.
Yeah you're right. I just recently figured that to get the spf and dkim alignment you have to set a custom mail from in the SES too and it significantly improves the delivery. Definitely makes sense to get your own servers as per your use case.
When forwarding email, we are receiving email from unknow domains. If we rewrite the FROM headers then the DKIM will invalid, so service will have to rewrite the FROM and clear out DKIM.
This is a well-known SES issue and project has to work around https://github.com/arithmetric/aws-lambda-ses-forwarder
``` For example, if an email sent by Jane Example <jane@example.com> to info@example.com is processed by this script, the From and Reply-To headers will be set to:
From: Jane Example at jane@example.com <info@example.com> Reply-To: jane@example.com To override this behavior, set a verified fromEmail address (e.g., noreply@example.com) in the config object and the header will look like this. ```
We want to forward email as it is and retain everything so we have to run our own postix in order to do that.