On Tue, Jan 03, 2006 at 08:14:06PM +0100, Maarten Fonville wrote:
> ah, I didn't set ftJabberPort.
> What does that port mean? The Socks port for the transfer on the jabber
> side? Is there any preferred port for it?
It's the port your Jabber client will have to connect to in order to
receive the file. I think any port will do, as long as it is opened in
your firewall (if any).
Best regards,
Lars
From [EMAIL PROTECTED] Tue Jan 3 22:08:07 2006
From: [EMAIL PROTECTED] (Maarten Fonville)
Date: Tue Jan 3 22:08:25 2006
Subject: [py-transports] Re: PyMSNt file transfer
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL
PROTECTED]> <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Lars T. Mikkelsen wrote:
> On Tue, Jan 03, 2006 at 08:14:06PM +0100, Maarten Fonville wrote:
>> ah, I didn't set ftJabberPort.
>> What does that port mean? The Socks port for the transfer on the jabber
>> side? Is there any preferred port for it?
>
> It's the port your Jabber client will have to connect to in order to
> receive the file. I think any port will do, as long as it is opened in
> your firewall (if any).
>
> Best regards,
> Lars
OK, thank you!
it's working now, but the transfers do not always work (read: sometimes)
often it just keeps on stalled... :(
Maarten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
iD8DBQFDuvXHXjGr8JbE19URAqh1AKDcDyQMwAJE3Wuts9HnJ+Wrwpja+QCgwnq8
mVbDNtekeJcUa2GXZZuYQ2A=
=zLn1
-----END PGP SIGNATURE-----
