Michiel Brandenburg wrote: > Well database and code could only assume that they get ipv6 addresses.
Ah, true. Well... the database I use (PostgreSQL) has a "network" type that accepts both IPv4 and IPv6 addresses. I'm not sure what the database I don't use (MySQL) does (or if it even has a network type.) > But then I guess there is no one stopping you encoding all ipv4 as 6 :) Right. I think that's what PostgreSQL may do... not sure. I'd have to test to see if it preserves IPv4-ness vs. IPv6-ness for the same address depending on the input syntax. > and I guess we can revisit when more of the world is using ipv6 .. like > in 100 years :) We'll all be using IPv6 when the United States uses SI units in everyday commerce. :( > I will see when I can get the patch altered not to take into account the > ipv6 mapped ipv4, as the c code handles that part. Don't worry about it... I've integrated a modified version of your patch into our development version. I'm travelling next week, but hope to release a (final?) MIMEDefang 2.68-beta after I return. Regards, David. _______________________________________________ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list [email protected] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
