Dear reader, Some more informations about our ftp/addon issue :
After doing some more tests and setting the pure-ftp server in debug mode, I can see that : pure-ftpd: ([email protected]) [INFO] New connection from ip-83-99-57-21.dyn.luxdsl.pt.lu pure-ftpd: ([email protected]) [DEBUG] Command [user] [xxxxxx] pure-ftpd: ([email protected]) [DEBUG] Command [pass] [<*>] pure-ftpd: ([email protected]) [INFO] opoce is now logged in pure-ftpd: (opoce at ip-83-99-57-21.dyn.luxdsl.pt.lu) [DEBUG] Command [type] [I] pure-ftpd: (opoce at ip-83-99-57-21.dyn.luxdsl.pt.lu) [DEBUG] Command [cwd] [jpublisher] pure-ftpd: (opoce at ip-83-99-57-21.dyn.luxdsl.pt.lu) [DEBUG] Command [epsv] [ALL] pure-ftpd: (opoce at ip-83-99-57-21.dyn.luxdsl.pt.lu) [DEBUG] Command [epsv] [] pure-ftpd: (opoce at ip-83-99-57-21.dyn.luxdsl.pt.lu) [DEBUG] Command [eprt] [|1|83.99.57.21|2580|] pure-ftpd: (opoce at ip-83-99-57-21.dyn.luxdsl.pt.lu) [INFO] Logout. An if a look Inside the RFC 2428, I can notice this : Finally, the EPSV command can be used with the argument "ALL" to inform Network Address Translators that the EPRT command (as well as other data commands) will no longer be used. An example of this command follows: EPSV<space>ALL Upon receipt of an EPSV ALL command, the server MUST reject all data connection setup commands other than EPSV (i.e., EPRT, PORT, PASV, et al.). Why then is the ftp library sending EPSV and EPRT to the server after th EPSV ALL ? Could this explain our problem ? Waiting for your comments, Guy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.xmlmind.com/pipermail/xmleditor-support/attachments/20070119/1cd5ee8a/attachment.htm
