The XMPP file transfer "proxy" setting is confusing.

[mcepl@…]

​http://bazaar.launchpad.net/~ulim/bitlbee/ulim-ft/revision/293 seems to be the only source of information about

Added an account setting 'proxy'.

Note that this is only used for sending. The default <local>; <auto> means let the receiver try a direct connection first and then the proxy discovered from the server (if any). If you know you're firewalled you can remove the <local>. If you want to provide your own proxy try something like

"<local>;JID,HOST,PORT". E.g.
"<local>;proxy.somewhere.org,123.123.123.123,7777".

Tried

account 0 set proxy "<local>;proxy.jabbim.cz,proxy.jabbim.cz,7777"

but I still get this

/dcc send public webm.txt
<root> jabber(mcepl@ceplovi.cz) - Trying to send webm.txt(22 bytes) to public@disk.jabbim.cz
<root> jabber(mcepl@ceplovi.cz) - Couldn't discover some of the server's services
<root> jabber(mcepl@ceplovi.cz) - File webm.txt: public@disk.jabbim.cz/jdisk accepted the transfer!
<root> jabber(mcepl@ceplovi.cz) - WARNING: Received SOCKS5 bytestream reply with unknown streamhost proxy.jabbim.cz
<root> jabber(mcepl@ceplovi.cz) - File transfer aborted: Couldn't establish transfer within 120 seconds
<root> jabber(mcepl@ceplovi.cz) - File webm.txt: DCC transfer aborted: Couldn't establish transfer within 120 seconds

and in the /QUERY with the public contact

* DCC SEND webm.txt with public timeouted - cancelling.

[Matěj Cepl <mcepl@…>]

It is possible, this could be something SELinux related. Although I am in a permissive mode, I have AVC denials on the filetransfer port.

[anonymous]

Currently the setting seems to be

account 0 set ft_proxies 'proxy.jabbim.cz'

[dx]

Really old ticket but who cares, the issue is still valid.

Apparently proxy.jabbim.cz resolves to 88.86.102.58 (rDNS hektar.jabbim.cz) but when asking through jabber for the actual IP address and port, it returns 88.86.102.51 (rDNS nezmar.jabbim.cz).

The problem here is that the user should really just have to specify "proxy.jabbim.cz" (like the "ft_proxies" option mentioned in the previous comment, which is how it's done with libpurple) and have bitlbee discover the actual IP and port automatically.

Sending this as a single line through the xmlconsole is a way to get that address:

<iq to='proxy.jabbim.cz' type='get'>
<query xmlns='http://jabber.org/protocol/bytestreams'/>
</iq>

[dx]

Added docs for this thing in ​aa3b61e178fbdb7069e171cc70c631ee63f72c8d

Keeping the ticket open with a different title because of what i said in the previous comment (it shouldn't be that complex)