- 新しい順
- 投票が多い順
- コメントが多い順
Hello! Thank you for reaching out.
Before addressing your query, allow me to explain that SES is an email service and the email flow looks like below:
Sender client application —> Sender MTA (SES in this case) —> Recipient MTA —> recipient mailbox application
MTA: Mail Transfer Agent (mail server)
Whenever SES receives an email from Client side it acknowledges back with the Message id i.e. after your application sends an email to SES, and SES accepts it for delivery (indicated by a message ID in the response). After SES accepts it, it will make an attempt to deliver the email.
Now, regarding your query, kindly understand that in SES we don’t have a mechanism that can validate the recipient before making an SES call. To achieve the validation of recipient, you can implement some feature at your application end.
Thank you
Hello, thank you for your reply!
Unfortunately, this did not answer my question, sorry for being a bit imprecise. The problem is that users can enter an email address that is valid according to the browser validation, but not considered valid by AWS SES. For example, 123@1234 is considered valid by browsers, but leads to errors when trying to send the mail.
Thank you very much again for your answer and the detailed explanation!