I dont recieve a mail for SES complaint notification when email marked as spam ?

260 views

I've managed to setup SES successfully and did some extensive testing. The only issue is that email complains do not seem to be reaching SES where bounce notifications work perfectly fine even though these are set exactly the same as complains (SES + SNS).
Testing via the Amazon SES Mailbox Simulator (complaint@simulator.amazonses.com) works fine, a complaint notification is being sent.

posted Apr 12, 2017 by Rahul Lokhandwala

Looking for an answer? Promote on:

Facebook Share Button

Twitter Share Button

LinkedIn Share Button

Similar Questions

+1 vote

Amazon Web Services and Simple Email Services

Anyone out there have success using PHP with AWS SES? I have an account and a PHP class. It was working at one point and stopped working all the sudden. I am having a problem even getting getting a response from AWS when using their API calls. Access and Secret KEY are correct. Email address verified. Clueless…

0 votes

When I update a branch in GIT from master I don't get the same files as when I create a new branch?

When I update my branch from master it pulls down several files, including some sass files. When I compile, however, gulp alerts me that I am missing .scss files.

I tested this by creating a new fresh branch and running gulp sass. This time there were no errors and I saw the missing .scss had been brought in.

Would anyone know why, on update, I am only getting some of the files from master?

0 votes

I am getting a 502 Bad Gateway error The Cgi was not CGI/1.1 complaint when I try to submit the empty fields .

I am working CGI project using C programming and I am reading the login detail in form input fields and when I try to submit the form with empty fields it gives me 502 Bad Gateway CGI was not in CGI/1.1 complaint.note that i am redirecting to the same page I am reading the the fields.

+1 vote

AWS EC2 Connection refused for http port 80 for tomcat server

I had installed tomcat 8 port 80 on Amazon AWS EC2, but netstat, fuser does show me tomcat on port 80. Browser gives 404 error and connection refused. I wrote to Amazon support for the misery...

+1 vote

AWS deployment best practices for Mongo?

I use Ubuntu if that matters. I install Mongo like I would on any Linux server, make sure to open certain ports through security groups, etc. Are there any best practices or perhaps specific EC2 support for Mongo I can leverage?

AFAIK Amazon doesnt provide RDS-like managed Mongo instances.

...