Maybe someone knows what the problem is. I can't properly set up receiving emails on SES and sending them to SNS.
There is a domain, conventionally #example.com.
I set up the rules set (active), rule, MX on the mail server, everything fine if I check it on mxtoolbox.com.
Pref
Hostname
IP Address
0
inbound-smtp.us-west-2.amazonaws.com
54.240.250.228 Amazon.com, Inc. (AS16509)
If I send an email from reply#example.com to any mail, then everything comes and is loggen via SNS, and when I want to receive email in reply#example.com, nothing happens on SES and nothing logged in SNS.
Maybe someone came across this?
Rule:
Recipients (All recipients under verified domains)
Actions 1. SNS Action Write email to SNS topic 111 using Base64
Related
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!
I had SNS working but understood I couldn't attach larger files to my messages but learned I could with SES. So I "connected" my SNS to SES using Configuring Amazon SNS Notifications for Amazon SES - Amazon Simple Email Service (I used the email address rather than domain).
After this configuration, I no longer received emails as I am in "Sandbox" mode. So, I deleted my email address from SES - nothing. I even deleted my email address from SNS topic and can't get any communication at all - even the "Request Confirmation" emails are not sent. It is not my Outlook service as I tested other emails.
Any advice would be much appreciated. I just want to get back to where I was able to send SNS messages.
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 am still in the sandbox of Amazons SES trying set a bounce email handler.
I am using the mailbox simulator to test a bounce/complaint email.
I have created a SNS topic (and I have subscribed to receive notifications from this topic):
I have selected this topic to receive bounce email notifications, then I have disabled email notifications:
However, when I send e-mails to bounce#simulator.amazonses.com from SES I still receive a bounceback e-mail and there aren't updates in the SNS topic.
I will try to make this issue clearer with some screenshots.
It can happen outside the sandbox too.
I did not realise that the Amazon SES console can set a SNS bounce/complaint topic for the domain, as well as a separate SNS setting for every verified email address.
So each verified email address can have its own different SNS bounce/complaint topic if you want! If you want them all the same, you have to go and set them all up in the console: tell each one to use SNS, otherwise they have 'Email Feedback Forwarding' set to "enabled" and this will override the setting at domain level.
The configurations of not receiving "Email Feedback" and sending Bounce emails to SNS Topic were set to my Domain example.com.
In my Verified Emails I had myself#example.com and I was sending e-mails with it.
It happens that my verified e-mail itself had these configurations too, so when I set them to be like those of my domain, everything started working.
If I had tried to send e-mails with anythingelse#example.com it would've worked.
Email Feedback Forwarding and SES notifications via Amazon SNS are exposed as two separate mechanisms. The linked documentation describes as much:
You must receive bounce and complaint notifications either by email or
through Amazon SNS – The default method is by email, through a feature
called email feedback forwarding.
Since you've shown that Email Feedback Forwarding is disabled, you are likely still receiving bounce notifications via your verified SNS email subscription.
To test, try removing your email subscription from the SNS topic and then sending an email to the bounce simulator again. To test further, you could subscribe a different email address or even an SQS queue to verify that bounce notifications are still being published.
I have an AWS SES application, which sends an email when an event happens. The mail deliver is successful when I send it to gmail. But, if I want to use my company domain address which is also verified by SES, I do not see any emails in my account. The confusion part is, the sender email (FROM) is my company domain address.
Simple way is to create a SNS subscription and a topic from Amazon console, if you are trying to send e-mails from you application you might have to see if your corporate SMTP server is able to recieve e-mails.
Another simple route is to use "sendgrid" service, this is a paid subscription and it is very easy to use.