- Newest
- Most votes
- Most comments
The situation you're describing could be due to a few different factors:
-
Delayed reporting: SES may sometimes show email send activity with a slight delay. This could make it appear that emails were sent at times when you didn't actually send them.
-
Queued messages: If there were any previously queued messages that couldn't be sent immediately, SES might attempt to send them at a later time. This could result in send activity appearing at unexpected times.
-
Retries for soft bounces: SES automatically retries delivery for soft bounces. These retries could show up as send activity at times when you didn't initiate new sends.
-
Complaints and bounces from old sends: Complaints and bounces can sometimes be reported long after the initial send. Recipients might mark an old email as spam, or an ISP might report a bounce for a previously accepted message.
-
Potential account compromise: If you're seeing send activity, complaints, and bounces for email addresses you're not intentionally sending to, it's crucial to investigate the possibility of unauthorized use of your SES account.
To address these issues:
- Verify your sending logs to ensure all sends are authorized.
- Check your SES dashboard for any unusual activity.
- Review your SES configuration, including any automated sending processes.
- Ensure your account credentials are secure.
- Consider enabling additional logging or event publishing for more detailed insights.
If you continue to see unexplained activity, it's advisable to contact AWS Support for a thorough investigation of your account activity.
Sources
Amazon SES Delivery problems - Amazon Simple Email Service
How to investigate what happened to the email that was sent via SES but was never received in recipient inbox | AWS Messaging & Targeting Blog
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 10 months ago

I strongly recommend rotating the SMTP user access key and the derived SMTP credential used by your lightsail application. If you are sending messages that you did not intend, it could mean that your SMTP user credential is compromised.
Set up condition keys on the SMTP user IAM policy, to ensure least privileged access: https://docs.aws.amazon.com/service-authorization/latest/reference/list_amazonses.html#amazonses-policy-keys
Automate the Creation & Rotation of Amazon Simple Email Service SMTP Credentials: https://aws.amazon.com/blogs/messaging-and-targeting/automate-the-creation-rotation-of-amazon-simple-email-service-smtp-credentials/
Archive outbound messages to see what you are unintentionally sending: https://aws.amazon.com/about-aws/whats-new/2025/02/ses-outbound-delivers-mail-manager-archives/