Although not using name.com, the explanation is quite sufficient, so leaving it here.
Basically, no DMARC adjusting for spam and possible attachments size limitation, in addition to no sending.
@peterbabic Not sure if this is widespread but there’s a nasty problem w/forwarding using namesilo, for example: #Namesilo (NS) will not blindly forward all msgs b/c NS worries about their own IP reputation. So NS has set up a very defensive server which causes legit emails to be refused or blackholed. NS gives less of a shit about lost legit msgs than about its own IP reputation.
@peterbabic #Email is extremely unreliable as it is without forwarding. Then you add domain registrar forwarding into the mix & it brings in more points of failure for ham loss. And the ham loss is very difficult to detect and diagnose (lots of finger pointing between the different suppliers). Perhaps that problem is unique to #Namesilo but something to watch out for.
@peterbabic I should mention that I use forwarding for all my email addresses in order to protect the address from widespread disclosure. This mitigates spam in the 1st place and makes it controllable, but indeed I've introduced more unreliability into the system. I simply try not to use email with friends or for anything important.
@peterbabic I can't say these are reliable but these are some forwarding providers that /seem/ reliable enough for things like bank statement notices, forums, or shopping/webshop accounts → erine.email, 33mail.com, anonaddy.com, simplelogin.eu, burnermail.io. Certainly i've found #spamgourmet.com particularly unreliable.
@peterbabic I reported the spamgourmet.com issues in bbs.spamgourmet.com but I don't think anything came of it.
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.