Can I buy email address for my new domain? - email

I've purchased a domain for a website that I will host on AWS but I could not figure out how to create a custom email address for this domain. I would like to have something like marketing#domain.com.
Is it possible to do this?
Thanks

Yes. AWS has two services for email, Amazon Simple Simple Email Service (SES) and Amazon Workmail.
These two services can both send and receive email, but they are designed for different purposes. You can read more about each in the links above, and decide which one is best for you.
Its worth pointing out that you can host your mail with any provider. You can do this by setting the MX records in your DNS to the values that the mail host you select provides. Common choices for hosting mail, that are similarly priced to Amazon Workmail, are Google Workspaces (which is gmail with your own custom domain), Microsoft365, and GoDaddy has an email only plan, but there are myriad of providers that offer mail for your custom domain.

Related

How can I create custom email

My domain is hosted at Godaddy and my project is at Digitalocean.
I want more than 15 custom emails, I know Godaddy offers email services but it is a little expensive for me. What I want is another services who offers create emails without transfer my domain name from Godaddy.
Thanks.
You can always purchase separate email service from MXRoute or Zoho, then please make sure you edit your DNS settings and point to correct settings.

Email protocol, mail server change and using another protocol from exist hosting

I have a domain which name is asifulmamun.info
Then, I've purchased a hosting for host website and connect this domain to hosting with cpanel by nameserver change.
I've create an email with this domain from Cpanel i.e. xx#asifulmamun.info.
Hosting provider told me that, my email has a limit for sending or receiving up to (25-30) email per hour.
But, if i will need to send/receive more than email from limitation how can I do this?
I think it's using my hosting server protocol for using mail email service.
Is it possible using another service provider protocol for using more than email from hosting server protocol?
Is it possible to use gmail server without purchase google cloude?
Is it possible, my domain will host in my exist hosting (Cpanel) and mail protocol using another service provider i.e. google, godaddy, aws or any service provider? If possible how?
Yes, you can use different service providers for incoming emails and for outgoing emails. In particular, you can use several email service providers for outgoing emails.
The "how" depends on what you want to do. I recently wrote a lengthy article on email. You find answers to all protocol-related questions there. The sections about email's architecture and its entities might be especially interesting to you.

Suggestions for email providers that allow mailbox creation via API and Forwarding Rules

I have a web application that utilizes several CRM types of emails for notifications, appointment reminders, attachments for digital sales and such. My clients can use my own admin domain email account to send these emails (no-reply email), or they can provide credentials for using their own SMTP server or relay service so that any emails that are replied to are sent to them (vs a no-reply admin email).
However, I'd like to try for a 3rd option where I can create an email mailbox on my a domain like so:
client1#mydomain.com
client2#mydomain.com
...
And then I would apply a forwarding rule on each one to send any replies to their personal email accounts so they wouldn't have to have their own SMTP service.
Now I can do this using providers' interfaces, but I'd rather do it with an API so I'm not having to manually create mailboxes and setting forwarding rules.
Currently I'm using AWS SES for my domain emailing, but I've searched for hours and the "solution" to create mailboxes and create rules to forward are ridiculous.
Are there any other email providers out there that make this easier? I don't need anything fancy except the ability to create a bunch of email mailboxes via API (preferably with a high limit of mailboxes) and the ability to create the forwarding rules via API.
Or can anyone recommend a good email provider that allows for a lot of mailboxes and makes forwarding really easy (and of course cheap).
Like "cringe" GoDaddy Email or something similar??
After a lot of research, this procedure doesn't really make sense these days. There are a lot of relay email providers that make it easy to set up "Senders" so that emails can appear to come from any kind of email account (personal or domain based) for ease of use with applications

How to send/receive email using Sendinblue with a Google Domain which has a domain pointing to Google Cloud DNS zone (where k8s hosts the website)

I am using Google Cloud for running a website, accessible on mydomain.com (fake, for illustration). I am trying to figure out how to receive email at support#mydomain.com (and let it be accessible by a human like a normal email) and also be able to send custom emails from info#mydomain.com programmatically. I am not sure what technology I am missing to be able to do this.
I have a k8s cluster with an Ingress with a static IP exposed through Cloud DNS zone. The NS records for mydomain.com. match the NS records on Google Domains. This works and I can access my website as expected.
From a little bit of research, I think I need to use something like Sendinblue because using their service will likely make my emails more legitimate. I purchased a dedicated IP in Sendinblue. Following this guide, I added ns1.sendinblue.com and ns2.sendinblue.com NS records for mail.mydomain.com in my Cloud DNS zone. I have associated the domain in Sendinblue and picked matching NS records. Then I created a sender and I am trying to verify this sender, but I have no inbox. This is the most confusing part. So I found this question-answer and followed by adding MX records and setting up email forwarding to mydomain+support#gmail.com (a plain Gmail account).
So now I expect any emails sent to support#mydomain.com to be accessible from the plain Gmail account. When I send emails, I do not receive them but I also do not get back a delivery failure. I've waited 12+ hours to make there isn't a DNS delay.
I feel like I haven't wired up these pieces correctly together and I am missing something but I am not sure what.
This is the answer publish by John Hanley added as community wiki since #John Hanley did not add as answer:
"
Select a normal mail service (Google Workplace, Office 365, Zoho (which offers a free account) and set up mail on your primary domain. Use Sendinblue as your email marketing tool - as it is not a general purchase email system
"

How to create an email account and set up email receiver when using AWS EC2 and SES?

So we are planning to use AWS SES for sending emails. But how do we set up the email receivers? And how do we create an email accounts? When activating AWS SES, it asks to verify an email account (eg. help#example.org)...
I tried to create a mail server on one of the instances using postfix following this article: http://flurdy.com/docs/postfix/, but it's not easy at all... Does anybody know any better alternatives?
Thanks.
SES is for sending email only. As you note, you must have some other way set up to receive email at least at the "From" address you intend to use, because Amazon will verify it before letting you send.
While you certainly could set up an email server and domain on an EC2 instance, it's very complicated. I recommend that you get an email service for just that purpose. If you only need a single address for all your messages, just get a free address from Google, Microsoft, Yahoo, etc.
If you need multiple addresses, consider getting Google Apps for Business, either for an existing or new domain name (it's easiest to set up if you have it register a new domain name for you). It's no longer free, but it's still quite cheap. A single user account can receive emails for every address in the domain, it's flexible, and it's reliable. It's a good companion to using SES for sending automated emails.
Use Amazon WorkMail if you prefer AWS. Gmail for work, Office 365, Hostgator, are some other examples. FYI, none of these providers simply provide domain emails. They come bundled with many other things such as chat clients, calenders, etc. Pricing of these services depends on what other things they are bundled with.
$4/user/month for AWS
$5/user/month for Google
$5/user/month for Microsoft
Since you are in AWS cloud, I will tell you a few things about Amazon WorkMail.
You get your own domain and 50GB of storage per user.
You get calendars for free.
You cannot use just any desktop mail client. You have to either use Outlook, or Mac's mail client, or the web interface. This is their weakest point. However, including other IMAP clients is in their roadmap (I guess atleast a year).
Integrates nicely with SES.
Important links:
FAQ page.
Features page.
There are many more features such as remotely removing emails from a device, managing your users, and so on.
What I can recommend you is to use Amazon WorkMail because they almost provide all the features supported by others, and you are tied with AWS anyway. AWS also recently launched Workspace and Workdocs (both separately billed) that will allow you to create a complete work solution. These services also combine nicely with IAM.