😄 Even the best stumble sometimes, right? I appreciate your understanding and I'm glad you enjoyed the tutorial! If there's anything else you'd like to see or if you have questions, feel free to reach out. Thanks for watching and your positive feedback!

Most welcome! Consider subscribing to the channel for more content!

You're welcome!

I'm glad you found the explanation helpful! Thanks for the suggestion, It was already on my list but I was having issues regarding the messages reaching out to my mobile due to mobile network operator, from the Amazon SNS service it was going all well, But I'll definitely consider creating a video on this, Stay tuned for more content, and thanks again for your support!

Hi, when you are in sandbox, AWS requires both sender and receiver mail addresses to be verified If you don't want to verify to address mail then you should move out of the sandbox and get a production access

Can you try generating new credentials for the same user and use the same ?

@@webwizard8 It still doesn't work after deploying to AWS, It works on local though

Thank you for taking time to comment, to address your query I'd recommend to use Nodemailer with SES transporter I've made a tutorial on this, please find here - kzfaq.info/get/bejne/nNqXfpl2x6fMqaM.html I hope this resolves your query and consider subscribing to the channel!

Good question brother When you are in the Amazon SES sandbox, you'll definitely verify your mail address because verifying mail identity is mandatory and you can send mail to the verified identities only. So if not verified you will get an error from Amazon SES service and in our code it will be caught by the try-catch block. In the case of production i.e. moving out of the sandbox - If you send an email to a non-existent or incorrect recipient email address, Amazon SES (Simple Email Service) will still process the request and return a response indicating that the email was successfully accepted for delivery. This is because SES doesn't verify the validity of the recipient's email address at the time of sending; it's responsible for relaying the email to the recipient's mail server. The response you receive from Amazon SES in case of sending to a non-existent or incorrect email address might look something like this: { ResponseMetadata: { RequestId: "abcd-efgh-ijkl" }, MessageId: "012345678901" } In this response: - ResponseMetadata: Contains metadata about the request, including a `RequestId` that uniquely identifies the request. - MessageId: Represents the unique identifier assigned by Amazon SES to the email message that you sent. Keep in mind that this response doesn't indicate the success or failure of the final delivery to the recipient's inbox. It only confirms that SES accepted the message for processing. The actual delivery status (bounce, delivery, etc.) will depend on the recipient's mail server and other factors. You might want to set up mechanisms to handle email bounces and monitor the status of sent emails for a more comprehensive view of the email delivery process.

@@webwizard8 that's wonderful answer but how to do set up and how can check from coding side. If mail is not sent. Thank you for your answer.

@@PankajKumar-gz1mt Well to handle bounces & complaints you have to setup Amazon SNS Bounces occur when an email cannot be delivered to the recipient. Amazon SES provides mechanisms to receive bounce notifications. You can set up Amazon SNS (Simple Notification Service) to receive bounce notifications. When you receive a bounce notification, you can mark the recipient's email as invalid or inactive in your system and take appropriate actions based on your business logic. I'd recommend to watch this video to get idea about handling bounces and complaints - kzfaq.info/get/bejne/pJl2pZOTqNmtpqM.html

with v3 the message is promise { false }

Promise { } promise will log pending as long as its results are not resolved yet. You must call .then or use await on the promise to capture the results regardless of the promise state (resolved or still pending) In the video, I've used async-await approach, Could check if you forgot to add await in front of send function call?