I am trying to mail S3 object by using Lmbda and SES services in AWS. Cloudwatch logs of lambda function shows that the mail is delivered successfully.
After testing further, I can see that the mail is getting delivered to only certain mail domains [ex: abc#xyz is receiving the mail but abc#def is not receiving the mail].
After subscribing to SNS topic, I could see that both [abc#xyz and abc#def] the mails have below same message.
smtpResponse":"250 2.6.0 010b01811af1d4fc-98135233-ebf2-4972-ae53-700ea8d2088a-000000#eu-west-2.amazonses.com 10358 bytes in 0.130, 77.489 KB/sec Queued mail for delivery"
Upon looking further, I got to know that many people were facing the same issue. But the mail got delivered in sometime for them. But in my case the mail is not getting delivered even after a day.
Can someone please tell me if there is something wrong with SES or the mail server?
Related
Due to a bug, our server started sending emails to the clients continously even after we removed the function that sends the mail. We are using Amazon Ses
AWS SES
I am creating a new application that will eventually send a lot of emails. Right now I can send emails using the API and I am receiving send and return notifications through SNS. Complaint notifications are processed correctly using the simulator (complaint#simulator.amazonses.com), but I don't get anything when I test gmail or outlook, or my company email accounts. I have enabled email notifications for testing, but this gives the same result. The simulator works testing complaint events. I can receive the events Sends, deliveries, openings and clicks using different emails
Please help.
SES has something called a sandbox. For you to be able to send emails to domains that are not trusted and specifically added in SES service, you have to go out of this mode:
Follow Amazon instructions to go into production mode: https://docs.aws.amazon.com/ses/latest/DeveloperGuide/request-production-access.html
I had SNS working but understood I couldn't attach larger files to my messages but learned I could with SES. So I "connected" my SNS to SES using Configuring Amazon SNS Notifications for Amazon SES - Amazon Simple Email Service (I used the email address rather than domain).
After this configuration, I no longer received emails as I am in "Sandbox" mode. So, I deleted my email address from SES - nothing. I even deleted my email address from SNS topic and can't get any communication at all - even the "Request Confirmation" emails are not sent. It is not my Outlook service as I tested other emails.
Any advice would be much appreciated. I just want to get back to where I was able to send SNS messages.
I am still in the sandbox of Amazons SES trying set a bounce email handler.
I am using the mailbox simulator to test a bounce/complaint email.
I have created a SNS topic (and I have subscribed to receive notifications from this topic):
I have selected this topic to receive bounce email notifications, then I have disabled email notifications:
However, when I send e-mails to bounce#simulator.amazonses.com from SES I still receive a bounceback e-mail and there aren't updates in the SNS topic.
I will try to make this issue clearer with some screenshots.
It can happen outside the sandbox too.
I did not realise that the Amazon SES console can set a SNS bounce/complaint topic for the domain, as well as a separate SNS setting for every verified email address.
So each verified email address can have its own different SNS bounce/complaint topic if you want! If you want them all the same, you have to go and set them all up in the console: tell each one to use SNS, otherwise they have 'Email Feedback Forwarding' set to "enabled" and this will override the setting at domain level.
The configurations of not receiving "Email Feedback" and sending Bounce emails to SNS Topic were set to my Domain example.com.
In my Verified Emails I had myself#example.com and I was sending e-mails with it.
It happens that my verified e-mail itself had these configurations too, so when I set them to be like those of my domain, everything started working.
If I had tried to send e-mails with anythingelse#example.com it would've worked.
Email Feedback Forwarding and SES notifications via Amazon SNS are exposed as two separate mechanisms. The linked documentation describes as much:
You must receive bounce and complaint notifications either by email or
through Amazon SNS – The default method is by email, through a feature
called email feedback forwarding.
Since you've shown that Email Feedback Forwarding is disabled, you are likely still receiving bounce notifications via your verified SNS email subscription.
To test, try removing your email subscription from the SNS topic and then sending an email to the bounce simulator again. To test further, you could subscribe a different email address or even an SQS queue to verify that bounce notifications are still being published.
I'm not receiving complaint notifications published into my SNS complaint topic, when i Report Spam in Gmail or Yahoo mail inbox. But, I am able to generate complaint notifications by using Amazon mailbox simulator. It perfectly works. Do i need to make some configurations to receive complaint notifications from Gmail / Yahoo mailboxes?The mail sending client subscribes using Http endpoint. Please note that all other notifications (Hard Bounces,Soft bounces, Delivered) are successfully received. I'm not running the email program in ec2 instance. It runs in my local machine and exposed to the internet using ngrok.
Note : I did run through other related questions in SO. But,they didn't help to resolve my case.