Hi All,

Sorry for the tardy reply.

--trace-ascii gives

== Info: About to connect() to ftp.btedinet.com port 21
== Info: Trying 193.113.146.122... == Info: connected
== Info: Connected to ftp.btedinet.com (193.113.146.122) port 21
<= Recv header, 68 bytes (0x44)
0000: 220 L2_EDI*Net EDI Direct FTP Service (EDI2.9 [EEA520.4.05]) Rea
0040: dy
=> Send header, 17 bytes (0x11)
0000: USER XXXXXXXXX
<= Recv header, 26 bytes (0x1a)
0000: 331 Password is required
=> Send header, 17 bytes (0x11)
0000: PASS XXXXXXXXXXXXXXxXX
<= Recv header, 25 bytes (0x19)
0000: 332 Account is required
== Info: Odd return code after PASS
== Info: Closing connection

-----Original Message-----
From: curl-users-bounces_at_cool.haxx.se
[mailto:curl-users-bounces_at_cool.haxx.se]On Behalf Of Daniel Stenberg
Sent: 19 January 2005 22:30
To: ian_at_firstb2b.net; curl tool talk
Subject: Re: FTP Account Request

On Wed, 19 Jan 2005, Ian Ford wrote:

> The FTP site that we are trying to connect to requires an account code
after
> the password. The FTP server prompts for this with the text "Account:"
after
> entering the user code and password. This causes cURL to exist with exit
> code 11.
>
> Has anybody successfully used cURL with such a set-up and if so how do we
> overcome the problem.

What is the exact server response that curl receives after the PASS ? Can
you
show us a --trace-ascii dump (with sensitive data edited out) ?

--
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html