I have a verified domain configured in SES. When I send an email with no-reply#my.domain, SES is not sending the email. If I use a valid email address from that domain, SES delivers them.
Does anyone know why this is happening? If my memory doesn't fail me, this used to work just fine as I've had this setup for years. Did something change recently in the AWS SES service?
I have looked for any mention regarding this and all I found is that the domain needs to be verified which it is.
Any help/insight would be greatly appreciated.
According to AWS SES documentation, such emails are hight not recommended
Avoid using a no-reply address, such as no-reply#example.com, as your
"From" or "Reply-to" address. Using a no-reply# email address sends
your recipients a clear message: that you aren't offering them a way
to contact you, and that you're not interested in their feedback.
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/tips-and-best-practices.html
In addition to the domain being verified, the sender email address that you want to use should be verified too. AWS will send you a mail to this address to confirm that it exists. If it doesn't exist, you can create a email receiving rule that will save the email into S3. You can then dig the verification link from there.
Related
Suppose I own an email 'demo#gmail.com'. Now, I create a new Microsoft account using my existing email. Thus I get another email 'demo#gmail.com', but this one is served by Microsoft.
So the situation is: one email and two providers.
If I send a hello email to 'demo#gmail.com' using my personal SMTP server, to which of the above will it send: will it send to the one hosted by Microsoft or the one hosted by Google?
How does it solve such an ambiguity? What are the factors that influence this?
This is a very common problem because many providers are giving us an option to create a new account using our existing email.
My observations:
I saw the emails inside the inboxes of both the services. I found that they had completely different emails.
There was no email which was common to both the inboxes. So there must be some mechanism to deal with it.
Let us look at the problem the other way round: If I had an email 'demo#outlook.com' initially and I created a new Google Account with this email address, then:
An email sent to this email address from another gmail account goes to the Google's server. An email sent to this email address from an Outlook also goes to the Google's servers.
There are two different ways of looking up an email. The 'normal' way:
You send an email to an server, in this example gmail.com.
Your mail delivery agent looks for mx record of gmail.comand send it to the ip-address of gmail.com.
If an email is delivered locally by the domain outlook.com it perhaps doesn't lookup the mx record, but lookups in a local database if the email-address exist there, and sends it to the ip-address of the outlook.com.
I think in the inbox of outlook.com are only microsoft emails.
More details can be found at https://www.socketlabs.com/blog/smtp-email-delivery/
I have a verified Domain in Amazon SES with a single email address. This address works fine and I can send and receive mails no problem.
I want to add a second email address to the domain, so I have copied the original account settings. There is a Rule Set for the new address that send to a S3 bucket and to WorkMail via an SNS topic. I can send mails from this new address. However the status is pending so I cannot reveive.
When I try to resend the verification email, the mail get sresent successfully, but I never receive the mail, neither in the S3 bucket nor in WorkMail.
What am I doing wrong?
You need to verify the email address by logging into the email client that you used to create that email address, and then clicking on the link that you get. So if you are using Workmail as your email client, just as an example, you need to create the email address there, and then add it to your list of addresses in Amazon SES and verify it. Summarized in 3 steps:
Create an address in whatever email client you use
Go to Amazon SES and add it to your list of email address identities in Amazon SES
Send the verification email
Go back to your email client (Workmail or whatever you're using to check your emails), open verification email, and click on the link
Now your rule sets should work.
I spend some time there... AWS has a trick there. Create AWS Work email(same you want to verify) first. Follow youtube videos-pretty easy. Then go to Amazon Ses and create email to you want to verify. The email will come to Amazon Work email. You will verify it from the web page mail application. After you need to ask Amazon to move your from Sand Box environment to Production. You will find links in SES. You fill simple form and Amazon will make it work for you. Then go back and delete Work mail or keep it(only costs 4USD per user)
I have set up Amazon SES for sending emails from my Java application. I also need to receive emails. I see that there is an option to receive emails using SES. But the docs are bit confusing. If I understand them correct, we can only receive emails from the domains that we own using SES.
The following doc says the same:
SES Doc
I just want to know if SES will help me to receive emails from or to various domains including Gmail or only from the domains I own.
You can receive emails from any email address/domain using AWS SES.
Edit: The process of verifying the domain is to prove that you own/control it (the domain), but once you verify it you can send email to any domain, and receive email from any domain. The verification has to do with allowing you to receive email for that domain, or send email via that domain - it has nothing to do with the domain of the people that send you an email.
Before you can receive email for a domain using Amazon SES, you must
prove that you own the domain by verifying it with Amazon SES.
Although Amazon SES enables you to verify single email addresses, you
must verify a domain if you want to use Amazon SES for email
receiving. You can verify and receive email with Amazon SES for any
domain that you own, but it is easier to set up a domain that you have
registered with Amazon Route 53.
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email-getting-started-verify.html
Currently Amazon do additional restriction. When you create new SES account, you are in sandbox.
However, when your account is in the sandbox, we apply the following restrictions to your account:
You can only send mail to verified email addresses and domains, or to the Amazon SES mailbox simulator.
You can only send mail from verified email addresses and domains.
You can send a maximum of 200 messages per 24-hour period.
You can send a maximum of 1 message per second.
To be able to send emails to different domain you should Moving Out of the Amazon SES Sandbox
To be able to receive emails, you must forward them to services like S3 or WorkMail for example
See also
Sorry if I have not understood something but (I believe) I have searched enough for this.
First things first: I have successfully set up my domain (mydomain.gr) which has been verified.
I have created a custom SMTP address (contact#mydomain.gr).
I have created a route which forwards everything sent at *#mydomain.gr to my personal Gmail address.
Test 1: If I send an email from an external address (something#something.eu) to contact#mydomain.gr it is forwarded to my personal Gmail. OK!
Test 2: If I send from contact#mydomain.gr to any external address (something#something.eu) I get the error Free accounts are for test purposes only. Please upgrade or add the address to authorized recipients in Account Settings. Of course the password is correct while sending. Otherwise another error is raised.
I think I have missunderstood some things...
So here comes my question:
How can I send email from my custom SMTP email address? (I do not wish to upgrade my account since this -free- Mailgun account will handle very small amount of emails. So, 10K are more than enough for me.)
OK. After some emails with the mailgun team I finally figure it out!
All I had to do was to upgrade my account (just enter credit card info). Now I can send email from contact#mydomain.gr to anyone.
Thank you mailgun!
I have also contacted Mailgun for the issue and get response back within few minutes:
This error occurs whenever utilizing either a sandbox domain or a free account without inviting users called Authorized Recipients.
Sandbox domains always require Authorized Recipients. With free plans, which are intended for test usage, all custom domains require Authorized Recipients. With upgraded plans, which are intended for production usage, custom domains no longer require Authorized Recipients.
Please take a look at the following Help Center article for more information about the Authorized Recipient process:
https://help.mailgun.com/hc/en-us/articles/217531258-Authorized-Recipients
Then I have add the Authorize Recipients and it works like a champ!
Hey all thanks in advance for the look.
We are attempting to develop a drip campaign email platform. For each "drip"we need to detect if the recipient replied to the email.
If so we would like discontinue the following drips.
For this we need some sort of reply detection but everything I have seen about tracking email metrics online is related to bounce rate and open rate.
Not much available on reply rate in terms of how to build such functionality.
Preferably we would like to do this on Amazon SES but if there is no such option we are willing to look at other smtp providers.
Perhaps there is some unique header we can save with the outbound email, then check against all the inbox emails. I guess this relates to how do email clients know to thread emails - perhaps it's a similar process.
Yes, you can fetch/read the email replies.
For that you will have to create 'Rule Sets' within the 'Email Receiving section' of SES.
The replies can be redirected to services like S3, SNS,Lambda, workmail to name a few and then you can read those from that redirected service