Sunday, July 21, 2019

Website Email: Amazon SES

Setting up email on my server isn't as straightforward as it may seem.  Amazon is concerned about their servers being used for email spam and have implemented restrictions, forcing you to request a lift on these restrictions or use their SES program.  However, with SES, the first 62,000 emails are free and it sounds like a legit service.  So let's do it.

ALL
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/quick-start.html

VERIFY EMAIL ADDRESS
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/verify-email-addresses.html

GETTING THE EMAIL ADDRESS IN THE FIRST PLACE
https://docs.aws.amazon.com/ses/latest/DeveloperGuide/send-email-sendmail.html

If you're using Amazon SES to send email from an Amazon EC2 instance, you should also complete the following steps:
  • If you're using Amazon SES to send email from an Amazon EC2 instance, you might need to assign an Elastic IP Address to your Amazon EC2 instance in order for receiving email providers to accept your email. For more information, see Amazon EC2 Elastic IP Addresses.
  • If you're using Amazon SES to send email from an Amazon EC2 instance, you should complete the Request to Remove Email Sending Limitations form. Requesting this change removes the sending limit restrictions that Amazon EC2 applies to port 25 by default.


IAM User Name: howtocureinsomnia.emailserver.iam

The new user will be granted the following IAM policy:
"Statement": [{  "Effect":"Allow",  "Action":"ses:SendRawEmail",  "Resource":"*"}]

IAM User: howtocureinsomnia.emailserver.iam

SMTP Username:
In OneDrive (in web folder not in remembers)

SMTP Password:
In OneDrive (in web folder not in remembers)


Scratch all that!  You should NOT be hosting your own webserver!

I just need an email name.

Email names come from some kind of email registry, the same way domain names come from a domain registry.

So I bought an email off of godaddy, but then found out godaddy doesn't control my domain - AMAZON does.  lol

So I am trying to link it up with amazon... shit... kind of wish I didn't pay for a whole year... well, at least I didn't buy the backup service or any other etc shit.


Trying to link all that up in Route 53, but it's tricky.  I am very unclear about the SRV records in particular, since amazon isn't really setup to accept the "protocol" and "service" fields.  I set it up via BOTH solutions offered at the below link, and now I'm just waiting 24 hours for my work to propegate so I can know for sure that it's failing verification.


More Research Indicates that Email DOES come from server??

With cpanel, for instance, you can create as many "users" as you want.

With Amazon SES, you can verify email with an S3 bucket, install the email server of your choice (like cpanel's), and get as many emails as you want.

So.. what... the... faackk... dad was wrong??






Amazon also has "Amazon WorkMail"


No comments:

Post a Comment