I have a unique name, think John Doe, and I’m hoping to create a unique and “professional” looking email account like johndoe@gmail.com or john@doe.com. Since my name is common, all reasonable permutations are taken. I was considering purchasing a domain with something unique, then making personal family email accounts for john@mydoe.com jane@mydoe.com etc.
Consider that I’m starting from scratch (I am). Is there a preferred domain registrar, are GoDaddy or NameCheap good enough? Are there prebuilt services I can just point my domain to or do I need to spin up a VPS and install my own services? Are there concerns tying my accounts to a service that might go under or are some “too big to fail”?
I can expand what hangs off the domain later, but for now I just need a way to make my own email addresses and use them with the relative ease of Gmail or others. Thanks in advance!!
That said, you can use a third party service only for sending, but receive mail on your self-hosted server.
That’s what I’m doing. I have selfhosted E-Mail with YunoHost and send it through SMTP2Go.
I’ve been successfully using SES for a couple years now without issue.
They rejected me for using for personal notifications. I get being strict but good God let me use your service and if I abuse it shut me down.
What do you mean, “for personal notifications”? I have a bunch of alert notifications that route through SES back to me. Never had an issue.
SES requires a manual review by their support to be able to send external emails. I was requesting for access to send to my Gmail notifications (and friends technically) from my self hosted services. They rejected my request.
Weird. I don’t remember my exact request but it was basically “send email on my personal domains” and they approved it.
Must have had a nice representative! Haha
Do you have more details on your setup?
I currently selfhost mailcow on a small VPS but I would like to move the receiving part to my homelab and only use a small VPS or service like SES for sending.
I set this up a couple years ago but I seem to remember AWS walking me through the initial setup.
First you’ll need to configure your domain(s) in SES. It requires you to set some DNS records to verify ownership. You’ll also need to configure your SPF record(s) to allow email to be sent through SES. They provide you with all of this information.
Next, you’ll need to configure SES credentials or it won’t accept mail from your servers. From a security standpoint, if you have multiple SMTP servers I would give each a unique set of credentials but you can get away with one for simplicity.
Finally you’ll need to configure your MTA to relay through SES. If you use postfix here’s a quick guide: https://medium.com/@cloudinit/sending-emails-with-postfix-and-amazon-ses-2341489a97e2
I’ve got postfix configured on each of my VPS servers, plus and internal relay, to relay all mail through SES. To the best of my knowledge it’s worked fine. I haven’t had issues with mail getting dropped or flagged as SPAM.
There is a cost, but with my email volumes (which are admittedly low) it costs me 2-3 cents a month.