From aa3b61e178fbdb7069e171cc70c631ee63f72c8d Mon Sep 17 00:00:00 2001 From: dequis Date: Thu, 27 Aug 2015 23:05:45 -0300 Subject: user-guide: add help for the jabber 'proxy' setting --- doc/user-guide/commands.xml | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) (limited to 'doc') diff --git a/doc/user-guide/commands.xml b/doc/user-guide/commands.xml index 403946f6..d8a6f840 100644 --- a/doc/user-guide/commands.xml +++ b/doc/user-guide/commands.xml @@ -1323,6 +1323,26 @@ + + <local><auto> + + + + A list of file transfer proxies for jabber. This isn't the connection proxy. Sorry, look in bitlbee.conf for those. + + + + It's a semicolon-separated list of items that can be either JID,HOST,PORT or two special values, <local> (to try a direct connection first) and <auto> (to try to discover a proxy). For example, "<local>;proxy.somewhere.org,123.123.123.123,7777". + + + The address should point to a SOCKS5 bytestreams server, usually provided by jabber servers. This is only used for sending files. Note that the host address might not match what DNS tells you, and the port isn't always the same. + + + The correct way to get a socks proxy host/port is a mystery, and the file transfer might fail anyway. Maybe just try using dropbox instead. + + + + lifo lifo, fifo -- cgit v1.2.3