I'm sending emails via AWS Simple Email Service but I have a problem. In the email I sent there is a verification problem. Unfortunately, it is bad reputation for our customer. We're using SES to send important emails about payment and subscriptions. That's why we have to make our customers feel safe. Is there anyone who knows why it happens or how I solve it? Thank's in advance.
Related
I am new to SES and thought it would be a quick setup but its looking a bit more involved than expected. I also have to go through a client so I want to make sure I understand my options before I make any requests.
So I have a client who has set up an email mailbox in outlook, dev#clientdomain.com. I want to have emails sent to this go into a lambda for processing, so I was looking at SES. Do I need to go through the same setup as if I was going to be sending emails? That is do I need to verify a domain identity or can I get away with verifying just an email? Do I need to ask the client to publish an MX record on their domain?
Tbh I was hoping I could just some email address in AWS that is linked to a lambda, and then have the client email forward to this. Is there nothing straight forward like this in AWS? I am able to send emails with the client email following this, but how can I receive an email and parse it with a lambda the easiest way?
I am trying to mail S3 object by using Lmbda and SES services in AWS. Cloudwatch logs of lambda function shows that the mail is delivered successfully.
After testing further, I can see that the mail is getting delivered to only certain mail domains [ex: abc#xyz is receiving the mail but abc#def is not receiving the mail].
After subscribing to SNS topic, I could see that both [abc#xyz and abc#def] the mails have below same message.
smtpResponse":"250 2.6.0 010b01811af1d4fc-98135233-ebf2-4972-ae53-700ea8d2088a-000000#eu-west-2.amazonses.com 10358 bytes in 0.130, 77.489 KB/sec Queued mail for delivery"
Upon looking further, I got to know that many people were facing the same issue. But the mail got delivered in sometime for them. But in my case the mail is not getting delivered even after a day.
Can someone please tell me if there is something wrong with SES or the mail server?
I'm using AWS SES to automate process of sending emails to my customers. I've confirmed my email address in AWS SES, so that it will use my email as a sender & reply to address. Sending works fine, customers are getting emails, but I'd like to have all emails send by AWS SES in my Gmail inbox.
My idea for that was to add BCC with my address to emails, so that email copy is being send to my Gmail inbox. The problem is that when I send a lot of emails my inbox gets messed. Because of that I wanted to mark all AWS SES incoming emails with some label to put them in separate directory. My problem is how to setup Gmail filters & AWS SES emails so that only emails send from AWS SES matches. I tried with setting from: filter to my address, but then all sent mails matches also, which is strongly unwanted behaviour. Do you have any better idea to have sent mails on inbox in a clean manner?
Thanks in advance!
Well you have probably set up the email topic yourself in SES. Therefore you can create a filter in gmail for a specific topic this way, just copy/paste your topic into the parenthesis:
subject:(Your Topic)
Hope it helps!
We use Amazon's SES service, and have set up Topics and Subscriptions under SNS (Simple Notification Service) so that we get notification emails when an email is bounced or successfully delivered. That's all working fine.
We sometimes send emails via SES on behalf of one of our partners, and before we can do that we need to verify their email address. The process is that the system asks SES to send out a verification email to the person saying "Example.com wants to send emails on your behalf, is that ok?", with a link for them to click. If they click it, then that email is marked as Verified within SES, and we can use it as a from address.
What I can't work out is how to automate the process of knowing whether they've clicked the link yet. I can log in to the AWS dashboard, and go and look at the list of verified email addresses, but i'd like to make it an automated process.
What would be ideal is if it worked the same way as bounces & deliveries: that i set up a "Verification" topic, and subscribe to it so we get an email like we do with bounces and deliveries. Then, the scheduled job that deals with incoming email notifications can say "Aha, this is a verification email for foobar#example.com: I'll mark their account as 'ses-verified'".
Does anyone know if it's possible to set this up? All the docs on the SES site just talk about bounces, deliveries and complaints.
thanks, Max
You can use the GetIdentityVerification api call in the SES part of the awssdk:
https://docs.aws.amazon.com/ses/latest/APIReference/API_GetIdentityVerificationAttributes.html
You could do this in a serverless way by having a lambda function do the check, and expose the lambda as an API endpoint to your application (among other ways).
Alternatively you could just try to send a single test email to a test/internal email address and check if it gives you an error - if its not verified, it will return an error immediately when you try to do the send.
EDIT:
If you want to use the CLI instead:
aws ses get-identity-verification-attributes --identities "mailbox#thedomain.com"
I have been trying to send mail with amazon ses and it worked very well for all the verified recipients. But i have a requirement to send mails to un verified recipients now. How to do this. Thanks
Your SES account is in Sandbox Mode. You need to open a request with AWS to take your SES account out of Sandbox Mode. This is documented here.
By default, AWS never provides you full access and needs certain
verification(s) to ensure security & remove possibilities of
Fraudulent activities or Spam.
These steps will resolve all the issue(s) regarding current scenario in your AWS SES Setup.
1) Verify “your-domain.com” Domain using the TXT record mentioned in Verification Tab - SES Console. By doing this you can use any ID in From Address to send emails.
2) Raise a Case on Amazon Support for Production Access. SES > Production Access. By doing this you can have the full access of TO addresses and can send emails to anyone.
Kindly let me know if you still face any issue.