SMTP configures by SES aws is going to spam folder

Question

We have configured a smtp with SES service of aws. we have also added DKIM for the service.

Our Reputation Dashboard shows:

But still our mails are hitting spam folder. We were previously using gmail smtp and it was working fine.

Could anyone suggest why this could be happening?

Will this do ?

I am not an expert. But i think it might help to set up a "MAIL FROM Domain". You are already doing DKIM. you can also set up custom "MAIL FROM Domain" as well. If you use Route53 to manage your domain, it will create MX and TXT records. the txt record is to setup spf record. you can give this a try https://docs.aws.amazon.com/ses/latest/DeveloperGuide/mail-from.html?icmpid=docs_ses_console — Arun Kamalanathan, Jul 27 '20 at 07:00
@ArunK i am already using Mail from Domain have those records as well in Route53 :). — sumanth shetty, Jul 27 '20 at 07:02
Not sure then. Is it happening for everybody. The only other thing i can think of is to request a dedicated IP address for SES. — Arun Kamalanathan, Jul 27 '20 at 07:05
@sumanthshetty you should use both, DKIM enhances what SPF is doing by signing any emails you send. However SPF allows mail exchanges to trust the source of where it was sent from. — Chris Williams, Jul 27 '20 at 07:28
@ChrisWilliams how would i add SPF Type record. What name and value should i give and which routing policies should i choose ? — sumanth shetty, Jul 27 '20 at 07:34
Thats fine, if you already have a text record for your route domain in value just append another line with the value `"v=spf1 include:amazonses.com ~all"` underneath the other value(s) — Chris Williams, Jul 27 '20 at 07:38
@ChrisWilliams , I have just edited the question have added an image. Hope i am following you right i have added the value "v=spf1 include:amazonses.com ~all" within the values of TXT record — sumanth shetty, Jul 27 '20 at 07:42
The SPF record should be added to a text record on the root of the domain (no subdomain) as its not a AmazonSES specific record — Chris Williams, Jul 27 '20 at 07:54
@ChrisWilliams I don't have Test record for the root domain i have only MX record. Should i add the Text record with these values for root domain ? — sumanth shetty, Jul 27 '20 at 07:57
For the SPF record only, yes make it if you don't already have one. — Chris Williams, Jul 27 '20 at 08:00
@ChrisWilliams i have created a SPF record for the domain with ""v=spf1 include:amazonses.com ~all"" value having simple routing. — sumanth shetty, Jul 27 '20 at 08:05
One last thing, this should be a `TXT` record ( I know its confusing), the type is not SPF (this is contained in the value). Other than that its perfect :) — Chris Williams, Jul 27 '20 at 08:08
@ChrisWilliams Have changed the SPF to TXT type. Hoping i am good now :) — sumanth shetty, Jul 27 '20 at 08:14
OK sure, added the answer of what to do. Let me know if you need anymore help :) — Chris Williams, Jul 27 '20 at 08:34

score 1 · Answer 1 · answered Jul 27 '20 at 07:35

1

Whilst you have DKIM this is only part of a solution, DKIM is actually used to sign your emails so that an email provider can be assured there was no tampering during the sending of the email.

You should also include an SPF record, this will provide the target mail exchanges with a record to say that sending an email from SES is to be trusted. With both of these in place your emails should not longer be marked as spam from a result of SES (after this it is purely reputation based).

For adding an SPF record for SES follow this documentation from Amazon.

answered Jul 27 '20 at 07:35

Chris Williams

32,215
4
30
68

The mail are still going to spam – sumanth shetty Jul 27 '20 at 09:20
Validation is now passing for this, unless the mail exchange has cached a record that does not exist it would purely be reputation at this point. Is it a specific domain having this go to the spam folder (they may now auto put this as a spam rule). Try another domain to validate – Chris Williams Jul 27 '20 at 09:25
when i try and send a test email by selecting the domain. i am able to receive it in my main folder. Could you also have a time to look at this https://stackoverflow.com/questions/63112120/error-while-trying-to-upload-file-into-s3-no-access-control-allow-origin-head – sumanth shetty Jul 27 '20 at 09:43
Currently we are owning only one domain. Basically if i understood your comment , you mean to say mail exchange might have cached the email from our particular domain which is moving it to spam? – sumanth shetty Jul 27 '20 at 09:58
I meant it might cache that theres no SPF record, or automate that its spam. IF you with another mail exchange receiving email as a test you can validate – Chris Williams Jul 27 '20 at 10:00
I feel so underwhelmed that i am not able to follow what your trying to explain. Could you please simplify the testing part as i understood the caching scenario. How can i test it ? – sumanth shetty Jul 27 '20 at 10:41
So if your domain `example.com` is sending emails to `foobar.com` and `test@foobar.com` is marking them as spam, try sending them to another domain `test@anotherdomain.com` and see if the scenario replicates – Chris Williams Jul 27 '20 at 10:44
Understood :) thank you for the patience. Man i trouble you a lot :) – sumanth shetty Jul 27 '20 at 11:03
1

Haha its fine :) – Chris Williams Jul 27 '20 at 11:08
need your help on this https://stackoverflow.com/questions/63117159/patch-method-with-lambda-integration-for-update-operation-on-unknown-number-of-p – sumanth shetty Jul 28 '20 at 07:38
Sure, was this question resolve or is it still open @sumanthshetty? :) – Chris Williams Jul 28 '20 at 07:39
still open. have to check with different mail exchange. As i am getting the test mail in my inbox and for others it is going to promotions or spam. WE have to try with different mail exchange other than GMAIL – sumanth shetty Jul 28 '20 at 07:49

SMTP configures by SES aws is going to spam folder

1 Answers1