I recently set up my amazon ses. and I have a verified DKIM and have published the SPF and senderid record from my DNS. When I send a sample mail from management console of SES the mail landed in the SPAM of hotmail.infact it is a verified sender as I am still in sandbox. I could not get much help from aws team either..
any help would be greatly appreciated
thanks
I have seen hotmail put an email in the spam folder when the html is malformed. Make sure your html is valid, and there are no unclosed tags.
This is not Amazon SES issue. You have to check with Microsoft why their Hotmail spam filters classify your domain email as junk. Note that they might also be looking at the content of the message and classify it as junk based not on the sender, but on what the body contains.
Amazon also has intermittent issues with blacklisting. It would be wise to check the SES forums to make sure that all is well with the SES IP you are sending from and that your email itself is not on a blacklist
Check the SES forums here
https://forums.aws.amazon.com/forum.jspa?forumID=90
Related
I have configured AWS SES for receiving emails to AWS S3 bucket. Followed Below Steps :-
Create Verified identities i.e. a#domain.com (using Email address so didn't setup any MX records).
Send a test mail from a#domain.com to another verified email address b#domain.com. It is working.
Setup Rule set to create rule :-
Status is Enabled
Spam and virus scanning is Enabled
Recipient condition - a#domain.com
Action - Deliver to Amazon S3 bucket (bucket created using SES so, policy is correct)
Got the file AMAZON_SES_SETUP_NOTIFICATION into the S3 bucket but whenever I receive any new mail to a#domain.com is not found in s3.
Rule set is also in active state.
Can anyone please help me why i am not receiving mail into s3.
Thank You
The error is in your setup. It is impossible for AWS SES to receive any information for the mail that you have, without specifying the MX records. Those records would point to the mail servers of Amazon, so that whenever an email is sent, it is received by them and they can process it.
The verified email addresses concept is used mostly for the sending. By approving the email address, you verify that you can use this email address to send on the behalf of it - not to receive the emails.
What is more, receiving an email works only on the domain level. So you cannot specify in the MX records the specific email addresses. The way to overcome this, is to use some subdomains for instance:
#a.domain.com to go to SES and normal emails will go to your normal email provider.
One last thing - the receipt rules in the amazon SES allow you for configuring the receiving emails on the specific address to give you the possibility to create the special address, such as no-reply/general/etc. Mostly you would prefer to have all of your emails routed in the similar way/routed based on the subdomain.
I have a fully functional Keycloak setup with verify email and then update password features enabled. I have tested multiple times and the mail sending part is working perfectly. But some clients reporting that they didn't receive the registration mail. This maybe due to their firewall, spam filter and so on, now I want way to check whether the email has sent from my system or not. Logs won't help at all, cannot find anything related to sent mails in logs.
we are trying to do mass e-mail sending via Amazon SES and we face issues. Hotmail and Yahoo receive in Inbox. Gmail receives in SPAM. We do everything we need:
non-blacklisted dedicated IP address from SmarterASP.NET (the hosting)
non-blacklisted domain: gmatpreptutor.co.uk prepared
non-spammy content checked with the newsletter we prepared and with
empty message as well - same situation, received in spam in gmail,
others - Inbox.
here are the headers:
https://gyazo.com/1f5cfc2f0b5041115d8dd1f85483d635
here is the other data in the message source:
https://gyazo.com/9cd7c6e4c50cb031625feb0a6201da04 we send from
Sendy
we host Sendy on SmarterASP.NET (windows hosting, without ANY hosting
issues)
Is there something that we need to do more?
Is SmarterASP.NET problematic for mass e-mail sending with Sendy,
using Amazon SES as SMTP, and why?
Is the domain in anyway problematic, from your point of view, and
why?
Is maybe dedicated IP address we purchased from SmarterASP.NET
problematic, from your point of view, and why?
Is Windows hosting problematic, from your point of view, and why?
What else?
Can Amazon team do any intervention so that this will not be issue
anymore?
Please, be as specific as you can, so that we can consider the best solution.
Thank you,
Ivan
So i have recently added and verified my mailgun account to my DNS & configured it through Exim through (WHM) on my server using the following guide.
enter link description here
It is now tracking my emails which is what i wanted, However on creating a new account through WHM and logging into the webmail into the new account i sent a test email to myself and i have at the bottom of the email "To unsubscribe click LINK"
As I'll be providing clients emails who will need to use emails daily i wouldn't want this link being under every single email they send.
I have upgraded my account, as i believed this would stop it but it hasn't?
Could anybody throw some light on this situation.
Many thanks
Log in to Mailgun, click your Domain Name and then disable the "Unsubscribes" option. This will then remove the link that is being automatically added to your outgoing emails.
When I am trying to send the email via amazon I'm getting the following error:
554 Message rejected: Sending suspended for this account. For more information, please check the inbox of the email address associated with your AWS account.
It happened a couple of days ago, with the endpoint eu-west-1. What can be wrong?
This seems pretty straightforward.
Sending suspended for this account.
You have been administratively blocked from sending email...
For more information, please check the inbox of the email address associated with your AWS account.
...and AWS has sent you a message about it, which should contain an explanation.
This is not a technical problem you can troubleshoot. You have apparently, whether intentionally or unintentionally, triggered a disruption of your service because of an excessive bounce or complaint rate or another apparent policy violation, or perhaps a billing issue.
You'll need to address this with AWS support.