On 2/24/22 3:42 AM, Jaroslaw Rafa via mailop wrote:
So you are not hosting entirely yourself. You are using a 3rd party provider to send the mail for you.Hosting your mail entirely on a home server (ie. using this server directly to send and receive, without a 3rd party provider), although theoretically possible, is very hard because of those 'dialup RBLs' you already mentioned. They are currently probably the largest obstacle to self-hosting a mail server at home, because they are widely used, and blacklist all customer/residential Internet connections with a dynamic IP address, and even some static IP addresses too...
PSA: I'm posting before I've had any caffeine. That being said....I feel that it's very important to differentiate hosting (everything) yourself (at) home from the IP address(es) that the world communicates with. Particularly germane is doing something like establishing a VPN between the server at your home and a (reputable) VPS provider wherein TCP port 25 is DNATed from the VPS to your home server and your home server egresses to the world via the VPS.
This separates where the hosting happens (your home) from the IP address(es) that the world sees (the VPS).
What I don't know is if this qualifies as "hosting entirely yourself". Does the reliance on a VPS to be an L3 endpoint break "entirely"? Does substituting the VPS with a box that you Co-Lo change anything?
Even after some caffeine, I feel like this is an extremely distinction as the VPN method allows -- what I'll call -- recreational postmasters to host their own email in their house without the reliance on 3rd party email providers. Not only does this /allow/ recreational postmasters, but I believe that it brings it within their reach for a reasonable effort.
-- Grant. . . . unix || die
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
