Nowadays it’s a pretty simple task to launch a mail server at home. Tools like Docker and virtualization can help us to run MTA in a few minutes. But you shouldn’t. SMTP wasn’t designed an insecure manner and SPAM is q global problem for that old standard.
In times of the old web, there were lots of small mail providers, but with the evolution of the web, most of the mails concentrated at big email providers, like Gmail, Hotmail, etc.
They started their epic fight against spam. DNSBL lists and manual IP blocks. And spammers started to extensively burn resources needed for sending mails. At some grade buying new IP stated to be more expensive than revenue from it.
And then spammers realized that each household has unique and private IP. And virus epidemic exploded on the internet. Infected programs sent millions of emails. And it was legitimate IPs.
At some point, big mail providers calculated that almost all legitimate emails received from data centers and servers on them. But almost all mails from home networks are spam.
Then big mail providers started to grade incoming mails also by as net records. Mails from residential IPs received a penalty as more suspicious. Of course, SPF, DKIM, DMARC, and other technical methods will allow the sender to bypass spam filter, but the probability of being trapped is much more from residential IPs.
Also, in a difference of home IPs — even virtual servers have static IPs. Another problem that in most home networks IPS is floating, that makes correct usage of SPF impossible. Even more — you can’t guess who was your predecessor, who controlled that IP before.
That’s why if you wanna send mails you should better rent SaaS services like G Suite, or at least setup server at Datacenter.
Team of Mailcheck