3 ms·
Has anyone has a weird issue where a recipient gets emails delayed by up to 45 minutes via SES, but sending via Google is received immediately? They aren't end
by cordite 9y ago
Has anyone has a weird issue where a recipient gets emails delayed by up to 45 minutes via SES, but sending via Google is received immediately?
They aren't ending up in a spam folder, just delayed.
Note that the email address domain is the same between these two.
- homero 9y agoIf you're new to ses, they can throttle emails to the same domains to protect you
- cordite 9y agoMmm, this recipient has their own domain and they only get one every two to three business hours. Other places with public (gmail, yahoo) or personal domains work just fine. Sendgrid exhibited the same behavior, last I heard, sendgrid is also using SES. But sending from a gapps email was instant.
- sethammons 9y agoI work at SendGrid. We don't use SES. All our receiving, processing, and delivery software (and more) is developed in-house. We also run our own data centers. However, we are looking at how we could leverage Amazon for more elastic scaling and faster API response times for our customers. But nothing with SES.
- cordite 9y agoThank you for the clarification.