I didn't plan on this, but it turns out that releasing my new book on running your own email server was SUPER TIMELY. #sysadmin
I didn't plan on this, but it turns out that releasing my new book on running your own email server was SUPER TIMELY. #sysadmin
@colin @a @mwl My experience using RBLs was that I needed to run DNS lookups on the same IP as the mail server which is annoying with socks.
If you have IPv6 at home, you can get a dual stack VPS and use proxy arp to relocate its ipv4 address to the other end of a SIT tunnel (ipv4 over ipv6) terminating on your actual server.
I used to have a web server set up this way.
@a @mwl @colin I've been looking at this solution. My email VPS (running for longer than I can recall) is still priced much higher than most.
So I'm thinking about just doing a 1:1 NAT on a (cheaper) VPS and letting my home machine handle all the real work.
In my case, it's to ensure all my _data_ stays on my machines, yet accessible from anywhere on the net. (My corp. blocks my webmail, but not Google or Kolab... I want to be a full peer, dammit!)
@a @mwl @colin Cryptographically impossible (assuming the cipher isn't broken which isn't a realistic threat).
Where compromises like the one you cited happen are by compromising one party in the cryptographic chain, not by breaking the crypto. With DANE the only parties who can potentially be compromised are your registrar, the TLD authority, and the DNS root.
@a @mwl @dalias Dang, I do use Linode.
On the bright side, yes, I have a Let’s Encrypt CA and DNSSEC/DANE, MTA-STS, CAA, and all the acronyms. I also edited the Postfix config files to require TLS for outbound connections to some servers that I know will never not support it, like Google, Microsoft, and a few others.