HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
[hylafax-users] Strange FTP behavior when receiving long list of faxes.
Hi, I'm developing a library for connecting to hylafax from windows
using FTP protocol.
I've some strange problem.
I launched a faxstat -vd and I saw that it use the LIST command.
-> PORT 127,0,0,1,213,33
200 PORT command successful.
-> LIST doneq
150 Opening new data connection for "doneq".
JID Pri S Owner Number Pages Dials TTS Status
if I manually connect from the same box to Hylafax FTP I cannot send
a LIST command, I receive "Invalid Command" but I can send a DIR
command that works correctly.
The strange thing is that connecting from a windows box with the FTP
from command line and I send the DIR command I obtain:
ftp> dir doneq
200 PORT command successful.
150 Opening new data connection for "doneq".
226 Transfer complete.
it seems that it doesn't receive results but if I try the same
command with a directory with fewer files, for example recvq I
receive result correctly:
ftp> dir recvq
200 PORT command successful.
150 Opening new data connection for "recvq".
-rw-rw- 8 10 xxxxxxxxxx Thu07AM fax000011274.tif
-rw-rw- 9 10 xxxxxxxxxx Thu07AM fax000011275.tif
-rw-rw- 1 10 xxxxxxxxxx 11Nov08 fax000010322.tif
.....
226 Transfer complete.
ftp: 22336 bytes received in 1,02Seconds 21,98Kbytes/sec.
This is the same problem I have with my library, I tested with
another ftp server with many files without problem. When there are a
lot of data to send Hylafax seems to send them in a different way,
maybe sending 226 before all data are sent, I don't know, but it
generates some problems with the client.
You have experience on this kind of problem? You can suggest me
something to do for better receiving data? Thanks in advance
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*