- 新しい順
- 投票が多い順
- コメントが多い順
Hello,
The doc you are referring to is correct. You should be checking your application log to make sure that it sends out the message directly, and there is no delay in conveying the message to SES. After that, you should be getting a message ID, and open a case with Premium Support. They will be able to pull out the internal logs and compare the different time stamps of the respective message, then advise where exactly the delay comes from. For example, if the message has been received from your application at 00:00:01, then it was sent out from SES at 00:00:01 and a response has been obtained from the ISP that the message has been received at 00:00:02, but your recipient is reporting that it has been received at 00:15:00, then the issue is with the ISP, as it has received the message and needed time to place that message in the inbox of the recipient.
Of course this is an example of how things go, but better open a case with Premium Support, and provide a message ID, and they will advise!
Best Regards, Mo
関連するコンテンツ
- 質問済み 6年前
- AWS公式更新しました 2年前