On Mon, 12 Dec 2005, Philip Hazel wrote: > > My current inclination is to generate an error on encountering an > incomplete IPv4 address.
I think this is the right move. The old Unix IP address parsing was partly a result of the slack coding that was normal at the time, and partly to do with old-style classful addressing. Neither of these are best current practice any more. In addition to that, slack IP address parsing has led to a number of security problems resulting from obfuscated URLs. It's a bad idea all round. Tony. -- <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> http://dotat.at/ ${sg{\N${sg{\ N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\ \N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}} -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
