Menu
I have switched to using Amazon SES to send our transactional alerts from our asp.net system and I'm getting calls that people are receiving duplicate emails.
I have confirmed that our program is only sending the email once to each user.
I received one of these duplicates exactly 5 minutes after the first email was sent, making me think it is some sort of retry issue.
Is there a way to configure/fix this issue?
If it makes any difference, I am using the AWS SDK in asp.net and calling the AmazonSimpleEmailServiceClient.SendEmail call.
980
A message placed in a spam folder indicates that Amazon SES has successfully delivered the message to the recipient's mail server (ISP). At this stage, Amazon SES has no control over the message and can't guarantee inbox placement.
Hard bounce – A persistent email delivery failure. For example, the mailbox does not exist. Amazon SES does not retry hard bounces, with the exception of DNS lookup failures. We strongly recommend that you do not make repeated delivery attempts to email addresses that hard bounce.
Pros: SES is basically the best email service out there. We find it the most used service out of all of the Amazon Web Services suite. - Extremely cheap, $0.10 for 1000 emails is the cheapest in the industry. - Reliability is top notch.
2) Raise a Case on Amazon Support for Production Access. SES > Production Access. By doing this you can have the full access of TO addresses and can send emails to anyone.
Amazon assigns a unique message ID to every email sent. Look in the full headers of the emails you received for an ID like the following:
0000012fea2d8375-85e23920-10cf-4d1b-b237-5dc13847b66c-000000@email.amazonses.com
If it is the same in both emails you got, then there is some sort of glitch between Amazon and the receiving SMTP server that is causing it to be resent. If the ID is different between the 2 emails, then you are sending it twice.
168
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
