Hello again,
I have confirmed that the problem is fixed by downgrading proftpd to
version 1.2.10 ( uh, 1.2.10-15sarge4 to be exact ), and it looks like
the culprit is here:

> 212.182.10.11 UNKNOWN ftpuser27 [25/Jun/2007:19:29:34 +0200] "PASV" 227 - (-) ()
> 212.182.10.11 UNKNOWN ftpuser27 [25/Jun/2007:19:29:34 +0200] "NLST" 226 - (-) ()

versus
> 212.182.10.11 UNKNOWN ftpuser27 [29/Jun/2007:18:17:20 +0200] "PASV" 227 - (-) ()
> 212.182.10.11 UNKNOWN ftpuser27 [29/Jun/2007:18:17:20 +0200] "NLST" 450 - (-) ()


the directory in question is empty, NLST results in '226' in 1.3.x, and in
'450' in 1.2.10.
It looks like 1.3.0 is causing 0-byte tcp connections here, which tend to
get blocked...

help?

--
Dariush Pietrzak,
Key fingerprint = 40D0 9FFB 9939 7320 8294 05E0 BCC7 02C4 75CC 50D9

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
ProFTPD Users List
Unsubscribe problems?
http://www.proftpd.org/list-unsub.html