Email forwarding with Amazon SES

[ntnsndr]

I recently switched an email address from sending via Cloudron to sending via Amazon SES. I was hoping this would improve deliverability and get rid of persistent errors around the PTR configuration. But now forwarding messages to a gmail address through Rainloop doesn't work. I'm getting this error:

This is a permanent error; I've given up. Sorry it didn't work out.

Intended Recipients: <ADDRESS2@EXAMPLE.COM>
Failure Reason: Error: 554 Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-2: ADDRESS1@EXAMPLE.COM


Original-Envelope-Id: <e4dce8d2-4e99-4de8-8c4d-10ac774a4fb7@EXAMPLE.COM>
Reporting-MTA: dns;my.medlab.host
Arrival-Date: Tue, 19 Aug 2025 14:47:08 +0000

Final-Recipient: rfc822;ADDRESS2@EXAMPLE.COM
Action: failed
Remote-MTA: 3.22.8.243
Diagnostic-Code: smtp;554 Message rejected: Email address is not verified. The following identities failed the check in region US-EAST-2: ADDRESS1@EXAMPLE.COM 

Obviously I cannot verify the addresses that people are writing me from, since I don't control those addresses or domains.

Is there a way to properly forward messages from arbitrary email addresses if using SES for delivery?

Thanks for your assistance.

[ntnsndr]

Bumping! A bit desperate for help here! Thanks:)

[nichu42]

This post is deleted!

[nichu42]

You want Rainloop to redirect messages so they appear as they come from the original sender?

[ntnsndr]

@nichu42 thanks for engaging. Honestly it could go either way. That does appear to be the default meaning of "forwarding" in the Rainloop filter. But it would be fine if all the messages came from the same address if need be.

[joseph]

Cloudron uses SRS for mail forwarding. Does SES support SRS? I think off late gmail has also changed behavior wrt SRS. I think @girish is aware of this already, there is no fix currently.