Duane Cathey was one of our friends who reported that curl -P [IP]

(CURLOPT_FTPPORT) didn't work for ipv6-enabed curls if the IP wasn't a
"native" IP while it works fine for ipv6-disabled builds!

In the process of fixing this, I removed the support for LPRT since I can't
think of many reasons to keep doing it and asking on the mailing list didn't
reveal anyone else that could either. The code that sends EPRT and PORT is
now also a lot simpler than before (IMHO).

tests/data/test212

@@ -15,14 +15,13 @@ ipv6
 ftp
 </server>
  <name>
-Get two FTP files with no remote EPRT or LPRT support
+Get two FTP files with no remote EPRT support
  </name>
  <command>
 ftp://%HOSTIP:%FTPPORT/a/path/212 ftp://%HOSTIP:%FTPPORT/a/path/212 -P -
 </command>
 <file name="log/ftpserver.cmd">
 REPLY EPRT 500 no such command
-REPLY LPRT 500 no such command
 </file>
 <stdout>
 data blobb
@@ -34,7 +33,6 @@ data blobb
 <verify>
 <strippart>
 s/^(EPRT \|1\|127.0.0.1).*/$1/
-s/^(LPRT 4,4,127,0,0,1,).*/$1/
 s/^(PORT 127,0,0,1,).*/$1/
 </strippart>
 <protocol>
@@ -44,7 +42,6 @@ PWD
 CWD a
 CWD path
 EPRT |1|127.0.0.1
-LPRT 4,4,127,0,0,1,
 PORT 127,0,0,1,
 TYPE I
 SIZE 212