I'm sending very simple transactional emails from SES. They always end up in my Outlook's spam folder. I've enabled DKIM signing.
The email body at the moment is very simplistic, and contains a header, two dates, and a link to sign into the app.
I've attached pics of my SES email and domain settings.
SPF should provide additional verification for emails, if I understand it correctly. SES has it's own SPF records in place but I have the same problem with Outlook and spam.
I also tried setting up the 'Mail From Domain' section on Amazon SES, but again, SES emails go to spam in Outlook. https://docs.aws.amazon.com/ses/latest/DeveloperGuide/mail-from.html
It seems the SES server that my emails originate from is on a few blacklists (5 out of 160). Perhaps that has something to do with it.
I can't think of anything else we can do at the moment....
DKIM signing does not guarantee your email won't be flagged a spam. I recommend reading this AWS blog post on the subject.
Related
I'm sending emails via this custom email address sales#decorbunny.a2hosted.com that I have but all the emails are ending up in spam. i have done all of the following authentications
DKIM (Domain Key Identified Mail)
SPF (Sender Policy Framework)
DMARC – requires you to already be using DKIM and SPF
I also tested the emails score here at https://www.mail-tester.com/ and its 10/10. But still the emails end up in spam. Can anybody please tell what can be the issue?
If you're sending bulk emails make sure the list your using isn't bad and that your email address isn't marked as a spam address by services.
If your emails contain links to fishy/sketchy websites then it can be marked as spam.
Your using too many images or too much images with too little text.
You're sending too many attachments.
Your recipient marked you as spam.
Your outgoing email information is incorrect/bad
If you're using a hosting service then contact your provider and see if something is up or if they can provide any insight! Email's are next to printer's in how fun it is to troubleshoot. Goodluck! If it's just one email your sending to that is marking you as spam then check it's settings if you can, or ask that email address owner to whitelist you, that is if your not sending bulk. Don't go asking 100+ people to whitelist your address lol
We've used Mailgun for 8+ years for inbound email routing, and always noticed lots of emails ended up in our spam folder(s).
After speaking to the Google team, it turns out that Mailgun is simply not compatible with Gmail when using inbound routes as it doesn't "relay" emails, but rather re-sends them modifying the headers.
This causes all emails to fail SPF! This means a certain (often large %) of your emails will end up in the spam folder for no good reason.
From Google:
"We've identified that Mailgun is re-sending those emails, while Google is expecting for those emails to be relayed. Re-sending emails causes the SMTP sender to change to [redacted]. What happens then is SPF is checked for [redacted]. Inbound gateway is telling to ignore Mailgun's IP address, so the previous one is being used instead. This would cause all emails to fail SPF.
In this scenario, it's recommended to contact Mailgun and ask them if there's a way to relay those emails, so that SMTP sender would not change."
Mailgun Response:
"Unfortunately, there isn't much that can be done to prevent this as this is how our Routes work"
Any solutions?
Has anyone managed to work around this issue?
Or does anyone have a fully-featured recommended alternative to Mailgun Routes?
I am sending emails through my domain and it receives to spam folder of clients. Even I heard that email sent to gmail account are also received to spam folder.
I check with my hosting provider for all necessary configuration related to email sending are configured correctly. I am using dedicated IP, separate cpanel account, PTR and DMARC are set properly and enabled valid DKIM and SPF records for my domain.
I also tested the spaminess of the domain using a third-party online tool and the results were 10/10 which means they are fully authenticated.
Another thing I double check the content of the messages with spam tables. The content of the email should not look like SPAM.
Please help me with this issue.
Best regards,
Vijay
I am using AWS SES and PHPMAILER to handle email sending in my system.
My question is, does the SES SMTP server automatically sign my emails with my DomainKey (DKIM) or do I have to do it manually using PHPMAILER?
On one hand, Amazon declares that they sign emails with DKIM, but on the other hand I see that you can add headers and sign emails with DKIM in PHPMAILER, so I don't really understand whose responsibility it is to sign my emails with it.
If you set up SES's Easy DKIM, all messages sent through SES will be automatically signed. You don't need to bother with having PHP handle that.
If you're sending email from a single domain (or small number of them) this is the way to go. If you are doing something tricky (like sending email on behalf of hundreds or thousands of domains) it might be easier to handle the DKIM signing in PHP.
I'm working on a digital gifting platform that relies on email reaching the inbox. Email is sent through Amazon SES, and has high quality (recipient's name in the email, single recipient, personally crafted message, extremely low bounce and complaint rate). However, I am still seeing very mixed results as to spam filter behaviour. Some get marked as spam some don't on the same ISPs.
I currently have no DKIM, SPF, or Sender ID set (http://docs.aws.amazon.com/ses/latest/DeveloperGuide/authentication.html)
Is there any downside to using all of these together, or should I pick and choose?
Your problem seems to be here:
I currently have no DKIM, SPF, or Sender ID
You definitely need SPF records to send email reliably from AWS. Due to ease of use, EC2 would be a spam haven without SPF. See this SO answer which describes how to configure SPF for use with EC2. Don't forget to fill out this form to request that Amazon remove sending limits from your EC2 instance.