I am looking into factors that may be affecting the deliverability of my emails, to make sure that the emails I send don’t go to the recipient’s spam/junk folder.
My email is a .pm address, instead of the commonly used .com or .net domains. Would that be a factor?
Would having my custom domain registered through njal.la be a factor? I read of some njal.la users failing spam check at spamhaus.org, but my address looks clean on there.
Would having my custom domain set up through addy.io be a factor? MX records are set up properly of course. Would it be better if I setup my custom domain through my email service instead? (currently on Tuta)
Would using Tuta to send my emails be a factor? If my custom domain is setup through addy, does it even matter whether I use Tuta or Proton or another email service to send emails?
Do you recommend any changes I could make to the points above that may be even marginally better for the deliverability of my emails? Thanks!
Yes, some tlds are treated more suspiciously than others. Since .com/.net/.org aren’t normally more expensive than exotic domains, you shouldn’t normally with the likes of .me/.xyz for email. The registrar should be a minor factor. A big factor affecting deliverability is the originating IP, but unless you self-host it isn’t something under your control.
I currently have a paid tuta subscription and I have my custom domain assigned to it in order to use custom domain aliases. I’m not particularly happy with the way it works because the system doesn’t protect you against replying to aliases using the wrong from address.
So for example, if I have an email received to alias1@custdomdomain.com and I have not pre-configured this alias in the tuta system, clicking the reply button will populate the from field with my default tuta email address and clicking the Send button will send it without any warnings, which I have done several times. What’s worse is the default tuta email address is actually your main Tuta email address unless you specify otherwise. Initially, I replied to several aliases with the from address set to my main tuta address again with no warning. This isn’t what I expected from a privacy/security focused email provider, hosting my custom domain for aliasing.
I also have a paid subscription to addy. io and if I’d hosted my custom domain with them, this would never have happened because their system automatically creates an alias record when an email from an unknown alias is received. However, the downsides to doing this are your emails pass through a third party and they look a bit odd in your mailbox because the from/to addresses contain the addy encoding.
I’m currently looking at Fastmail, who seem to provide a much more comprehensive way of managing custom domains in particular an “always reply to the from address” setting which for me is essential. It maybe that I can replace my Tuta and Addy subscriptions with fastmail performing both roles.
(BTW no gripes with Addy.io, great tool, great support, works perfectly)
It absolutely will. This registrar in particular gets its domains flagged as spam fairly often. If this happens, you will have no recourse. Use another registrar