Bug #1286
[winston] IPv6 is badly mis/not-configured; email issues
90%
Description
proton.parabola.nu has no public IPv6 address, but it does have an IPv6 address via lvpn. So it thinks it has IPv6. So, when delivering an email, if it sees an AAAA record, it thinks that's a fine address to deliver to, but if it tries to connect, it will get "network unreachable". On the other hand, it might just happen to choose the A record, and everything is happy.
So, SMTP servers that are accessible via both IPv4 and IPv6 intermittently have emails dropped.
Related issues
History
Updated by lukeshu about 7 years ago
This probably only became an email issue on 2015-05-29 when fauno changed main.cf:inet_protocols from ipv4 to all when adding LogJam mitigation.
Updated by lukeshu about 7 years ago
I've emailed n1md4 asking about getting an IPv6 address for proton.
Updated by lukeshu about 7 years ago
- % Done changed from 0 to 20
I've set inet_protocols = ipv4 for now, as a workaround.
Updated by lukeshu about 7 years ago
n1md4 informs me that an IPv6 address is not available for proton.
Updated by lukeshu almost 5 years ago
- % Done changed from 20 to 100
- Assignee set to lukeshu
Fixed. I've set up a HE IPv6 tunnel.
Updated by lukeshu almost 5 years ago
- % Done changed from 100 to 90
- Status changed from fixed to confirmed
Wait, I screwed up IPv6 rDNS, so some IPv6 mail servers were rejecting
our email (including my mav.lukeshu.com).
I've fixed the rDNS, and have disabled IPv6 in postfix until the 24
hour DNS ttl expires.
Updated by lukeshu almost 5 years ago
- Subject changed from [proton] IPv6 is badly mis/not-configured; email issues to [winston] IPv6 is badly mis/not-configured; email issues