Transferring Domain to Route53 - Email Access - amazon-web-services

I am helping out a friends business who have had a falling out with their web developer, and I want to transfer their domain to Route53.
I have the domain password so I am going to shift everything across to Amazon.
However the email accounts "info#domain.com" and "admin#domain.com" were set up by the other developer, who have unfortunately cut all communication between my friend and them.
My question is what will happen to those email addresses after I transfer the domain, I presume they will shut down? Is there anyway to determine where an email account is hosted and thus determine it's MX records for Route53?
If they lose the account is it possible to register new emails with the same address after the transfer?

If you control the DNS servers, you can switch the MX record to a new host, which will give you complete control of your email.
You can do this in Amazon with Workmail, or set up something like gmail.
Any new emails will come into the new server. You will not have access to any of the old emails however.

Related

"A statement of the security measures and mechanisms you will be implementing" AWS (Unblock port 25)

I tried to unblock port 25 on my ec2 instance so I could send emails and I was asked to provide this:
A statement of the security measures and mechanisms you will be implementing to avoid being implicated in the sending of unwanted mail (Spam)
What does this mean, like what is an example of those security measures? I have no idea what I'm supposed to respond to with that. All I plan on doing is sending emails to verify email accounts and change passwords for user accounts on my website.
AWS actually restricts access to this port for security reasons. The suggestion is try using another port if you can (for example SES works over port 587 as well).
You can however request that this restriction is removed, to do this you will need to do the following steps:
First, create a corresponding DNS A record:
If you're using Amazon Route 53 as your DNS service, either create a new resource record set that includes an A record, or update your existing resource record set to include a new A record.
If you're using a service other than Amazon Route 53, ask your DNS provider to create an A record for you.
Then, request AWS to remove the port 25 restriction on your instance:
Sign in with your AWS account, and open the Request to Remove Email Sending Limitations form.
In the Use Case Description field, provide a description of your use case.
(Optional) Provide the AWS-owned Elastic IP addresses that you use to send outbound emails as well as any reverse DNS records that AWS needs to associate with the Elastic IP addresses. With this information, AWS can reduce the occurrences of emails sent from the
Elastic IP addresses being marked as spam.
Choose Submit.

Google Domain and G-Suite with AWS instance

I have been looking around the internet and I have come across a few different ways to link my AWS EC2 instance to my domain name. It looks like I could do it using Route 53 but I am not entirely sure on that process. The other way is to map it from google. These seem like the best instructions I have found for that: link a Google Domain to Amazon ec2 server
The question that I can not seem to find is what about my email address. I pay google so that I can have some email addresses name#mydomain.com. Now these work fine and I have had them up and running for months. But now I want to have my website (it is a web app) point to it. Because currently when you go to mydomain.com it says This site can’t be reached mydomain.com’s server IP address could not be found.
Some help here on how to do this would be great. I am afraid that I am going to set this up incorrectly and then lose access to my gmail account which I cannot have happen.
Your domain's email is configured via MX DNS records. You would point your domain to your EC2 instance by adding A or CNAME DNS records. The two configurations are completely separate. You will not break your current email setup by adding an A or CNAME record that points to the EC2 instance. You simply need to add that record in your DNS settings, wherever your DNS is currently hosted. You don't need to make any changes in your Gmail account configuration, and you don't really need to use Route53 either (although it does add some nice features). You had to configure the MX records somewhere at some point, to setup your G-Suite account for your domain. You just need to go into that same DNS configuration (most likely still hosted at the company where you initially purchased the domain name) and add an additional record.

Receiving Incoming Email on Google Compute Engine Hosted Domain?

Current Setup :
Domain registrar - Godaddy.com
Domain Hosted on - Google Cloud Platform
CMS - Wordpress
I have a simple Wordpress website that is hosted on the Google Cloud Platform free tier. For any emails that need to go out of Wordpress (Password reset mails / notifications etc.), I have configured SendGrid as the SMTP relay and it works perfectly.
My problem now is how to receive incoming emails ?
I just want to setup a couple of email accounts for my domain and forward / import all incoming emails to my Gmail account.
All instructions point to Gsuite, which will be an overkill at this time since I will not be using any of its features. I just need to receive occasional incoming emails.
While there are literally 100's of articles on configuring outgoing emails via SendGrid / MailJet etc., there are no useful articles on how to receive incoming emails.
Google search mostly turns up an old video about using a free Zoho account; which itself is now become a paid app.
Tried so far :
[1] Tried to set-up email forwarding on Godaddy. Nothing worked. Since the Nameservers are pointed to Google Cloud DNS, I believe Godaddy forwarding will not work.
[2] Checked SendGrid options, could not find anything.
[3] Trawled through Google for several hours, could not turn up anything useful.
I would sincerely appreciate any relatively straight-forward solutions / suggestions / pointers for receiving incoming emails - Either through the GCP or outside.
Just add an mx record to your domain that point to the IP address of the machine hosting your mail service .
Here's how you can add the record :
https://godaddy.com/help/add-an-mx-record-19234

How to route Gsuite email's through Amazon SES?

So I have my amazon SES account, my Gsuite account, and my domain DNS settings.
I used Route 53 to generate my DNS stuff and used "use other name servers" and then entered my Amazon Route 53 name servers instead. I also added Gsuite MX records within my Route 53 and INBOUND WORKS...
However, I cannot for the life of me get outbound to work using my SES account. I tried generating an SMTP key on SES but cant find where to put it in Gsuite settings. I called Google and they said you need to put Googles SMTP settings into amazon but cant find that either... I just want to use Gsuite UI while having the emails sent out via my SES account.
On a smaller note, I'm having SPF verification issues too. I added "v=spf1 include:amazonses.com -all" on my Route 53 settings but it's saying "You are not allowed to use one of your sender email addresses" and throwing my emails into spam.
I'm not the most technical guy so a lot of it is learning as I go so any help would be appreciated.
Thank you all again!
Looks like you are not clear on where things should be.
Your MX records are only receiving incoming emails, you can use any number of outbound servers as long as you verify those ones.
Send email via GSuite sould work fine, since GSuites verifies all your identify with the DNS entries.
SES Process:
Verify your domain -- Follow the instructions given by SES to verify your domain.
Verify your from Email Addresses
This is essential, you are sending email, if someone replies you should be able receive the email back. In your GSuite, create an alias or new user to receive the email address you want to in From when you send your emails.
Verify your email address from SES and you will receive an email to your inbox and confirm your email address. You can also enable DKIM setting along with this process.
Apply to AWS Support that you are going to send production emails.
Now send emails using SES API,
http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/SES.html#sendEmail-property
Using SMTP from gmail:
If you want to use SMTP from gmail, you can completely skip SES at all,
Use the following packages, enter your gmail credentials and send email.
https://www.npmjs.com/package/nodemailer
https://www.npmjs.com/package/gmail-send
You can also search for other packages online to get the best that simplify your needs.
You also need to need to note, if you use gmail as your outbound email, there may be limits on how many emails you can send outbound.
Also with SES you cannot send spam or non-transactional emails without the consent of the user. Make sure you follow all those standards.
Hope it helps.

Setting up custom email addresses for domain bought from Digital Ocean

I have a domain name hosted on digital ocean, 'www.mydomain.com' and hosting an application made in django. I need to create an email address 'me#mydomain.com'. I have searched on a way to do this from start to finish but cant get a definite answer. Need some guidance.
Digital Ocean does not provide an e-mail component. You can either install and setup your own e-mail server from scratch, which you don't want to do. Or use an e-mail hosting service provider, zoho.com is a free one. There are others. Rackspace, and Google offer e-mail host solutions, but they are both fee-based.
Once you sign up for an e-mail hosting account, zoho.com or whichever e-mail service provider you choose will provide you with an MX record setup. You will then add an MX record to your DNS records on your Digital Ocean domain.
This will connect your domain name to the e-mail hosting service.
After this, you need to setup your e-mail on the e-mail hosting service. THis is a non-trival task and you'll have to do reading on SMTP, POP, IMAP etc. There is plenty of help on the zoho site.
Make sure to test sending and receiving e-mails to make sure the setup is working.
Once you have working e-mail on your domain, then you can move on to using it in your Django app.