title: AWS SES emails always go to Spam even after verification
body: <p>I am sure many asked the same question but I can't find an answer that is comprehensive.
  We are running a web app (myapp.com) on an EC2 instance deployed on the Sydney region. The app sends emails via AWS SES. Because SES is not available in Sydney, we have configured SES in Oregon. We generated the SMTP credentials and configured our Springboot application to send emails using these credentials. We are able to send the email and the email gets delivered successfully but it goes to the SPAM folder.
  The email from address is: noreply@myapp.com
  We have verified the domain name in the SES console
  We have verified the noreply@myapp.com email address in the SES console
  DKIM is also turned on and verified </p>
  
  <p>However,
  We are not sure why the email keep getting delivered to the SPAM folder.
  When I viewed the RAW email message I can see the SPF header:
  SPF:    NEUTRAL with IP xx.xx.xx.xxx
  I haven't configured any SPF record in my DNS name but as I understand it I don't need to because I am using SES SMTP server and not custom MAIL FROM.</p>
  
  <p>I am at lost as to why the email is getting delivered to SPAM.
  Can any one help?</p>