SES has rule sets for receiving email. I have one rule that matches all the blocked recipients (addresses at my domain that receive spam), which bounces with 'mailbox does not exist' (then stops rule processing), then another rule after that that puts all mail into an S3 bucket.
Then I have a script that uses the AWS CLI to move all the mail from the bucket to a local dovecot server.
The whole thing is really hacky/experimental at the moment, and I haven't given out any addresses, so all that I receive is spam. But the spam I do receive is very little and quickly adds to the blocked recipients list.
Sending using SES uses the built-in SMTP server functionality at AWS and has very generous limits for one who is not marketing.
I presume the parent means Amazon work mail which AFAIR uses SES to send. Last time I evaluated email services, they didn’t handle catch-all which made that a non-starter for us.
