ScottPeterJohnson
ipv6 support
Comment by someone on July 5, 2021: @Scott The lack of ipv6 is very huge issue. I think it's worth mentioning in the list of drawbacks that there's no ipv6 support.
Comment by Scott on July 5, 2021: What's your use case that makes it a huge issue?
Comment by someone on July 7, 2021: I can't access purelymail in ipv6-only environments. That's the huge issue for me. ipv6-only environment is my main workflow and email is essential part of it. Second reason is that country where i live has a tendency to block email services like that - protonmail, tutanota, cock.li, etc.. all are banned. For some reason, censorship doesn't affect ipv6 provided by my ISP. Having purelymail reachable over ipv6 would save me from situation when it will be eventually inaccessible due to censorship. Don't suggest me VPN/proxy because it's actually overkill when there's already native ipv6 that can successfully bypass restrictions.
Comment by Scott on July 8, 2021: That seems reasonable- I have no real objections to providing IPV6 for the user SMTP/IMAP/etc services, it'll just take a bit of technical dev and fun configuration. I probably wouldn't provide it for public SMTP yet, but it sounds like you wouldn't notice anyway.
There is a shortage of IPv4 addresses in Africa and Asia. In Japan, it is widely practiced for ISPs to provide NATs and share a single IPv4 address with multiple subscribers.
In Africa, the situation is even more serious, and home ISPs (not hosting ISPs!) that provide only IPv6 that offer only IPv6 are emerging.
Definitely seems like a big thing to sort out then! I'll add it as high priority to see if we can't get it worked on in the near future
