Earlier quoted context omitted.
It is not a conspiracy theory that it is hard to maintain reliable delivery with self-hosting email. It is primarily because email filters are in part based on trust relationships, and huge amounts of spam come (or at least, did) from relatively unknown originating servers.
Spam does not work with email addresses using IP literals.
What DMARC Protects You From, and What It Does Not
41–47 of 47 posts
Re: What DMARC Protects You From, and What It Does Not
#42Earlier quoted context omitted.
I think DMARC is missing support for homing pigeon characteristics such as the markings and colors on its crest and plumage. As being self-hosted, without paying the IANA and ISP mob, I am still blocked to send email to gmail.com.
Regulation on small tech interop is exactly for guys like you.
Re: What DMARC Protects You From, and What It Does Not
#43I think DMARC is missing email address with IPv[46] literals support. As being self-hosted, without paying the DNS mob, I am still blocked to send email to gmail.com because such email addresses do throw out of whack gogol code. Email addresses with IPv[46] literals are intrinsincly stronger than SPF. If in the envelope or any of the 'from' headers (if my memory does not fail me, there are few more headers to scan),…
Most people don't own their IP range so it's moot point to support it.
Re: What DMARC Protects You From, and What It Does Not
#44Re: What DMARC Protects You From, and What It Does Not
#45Re: What DMARC Protects You From, and What It Does Not
#46Earlier quoted context omitted.
I think he reposts them on his consulting page https://www.sh.consulting/blog and no, I am not affiliated. Just keeping an eye on the email deliverability topic as a hoppy.
Do you mean as a hobby?