Member OP
IPv6 only hosting in 2024 still broken! I tried to run a mail server on pure IPv6 and half the internet just drops packets! MX records fail! Reverse DNS nightmare! Who is actually making this work without NAT64 crutches! Tell me your secrets or confirm im right to give up!
Ipv4 is not dead yet 😊 mail needs it reputation systems are slow really slow try dual stack or accept the pain
We've seen this pattern repeatedly with IPv6-only mail deployments. The practical issues:
Our stance at RackNerd: we offer IPv6-native but recommend dual-stack for mail. Free tunnel options exist if your budget is tight — https://www.racknerd.com
— Admin
Which tunnel? Hurricane Electric still works but good luck with that MTU on mail. I ran HE.net for a year, SMTP sessions timing out halfway through the banner because of fragmentation. Gave up.
Member OP
This. HE tunnelbroker is the default answer and it is a trap. Works for ping, dies for real traffic. I wasted a weekend on this.
Toronto here. My upstream (Rogers) finally gave me a /56 but their reverse delegation is broken. Had to keep my VPS at BuyVM Montreal for mail because they handle rDNS properly. IPv6-only at home is a fantasy for now.
Member
BuyVM is good but they are IPv4+IPv6, not IPv6-only. The original question is about pure v6. I tried Hetzner's v6-only instances in Falkenstein and mail was a disaster. Gmail accepts it, Yahoo does not, Microsoft is 50/50.
Following this because I want to believe. My side project is on Vultr v6-only in New Jersey and the only thing that works reliably is outbound to Cloudflare. Everything else is grief.
Yahoo has v6 MX since forever but their spam filters are stricter on v6. No reputation history = auto junk folder. You need to warm up an IPv4 IP and pray they link it, or accept that v6 is second class.
What about running mail through a relay? AWS SES, Mailgun, whatever. Keep your v6-only host, let someone else deal with delivery. Not pure self-hosted but it solves the actual problem.
