- Newest
- Most votes
- Most comments
Thanks Jesse, for me that does indeed work.
For normal people and clients using this, just sending out emails with no interest in how it all works behind the scenes, it is not really a solution sadly.
You can subscribe to the events to see this level of detail. https://docs.aws.amazon.com/ses/latest/dg/monitor-using-event-publishing.html
No real answer or solution sadly, apart from what's in this thread. Sorry ;-(
This is a real problem as I now have an inbox filled with emails from auto replies concerning "Out of Office" and there is no indication of where these emails are coming from. There MUST be a way for SES to use the correct FROM address.
I'm now running into this issue where the OoO email is bouncing back to me without the data of who sent it. It used to have details in the body, but no longer. Any way to figure out how to get this back so that I can properly catch the event and process?
Relevant content
- asked 3 years ago
- asked 9 months ago
- asked a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
I agree with OP, AWS SES does not behave in a way which is useful in all use cases. I also need to receive OoO messages verbatim, with the original Sender/From not being overwritten by MAILER-DAEMON@region.amazonses.com. And I also don't consider that OoO is a "bounce" in my use case, because the message is still delivered to the user.
Also, indeed, it is possible to subscribe to events to get details about bounces, but sometimes OoO messages are qualified by AWS SES as having UNDETERMINED bounce type. To see that in action, it is enough to send a message to the OoO simulation email: ooto@simulator.amazonses.com