diff options
| author | dequis <dx@dxzone.com.ar> | 2015-08-27 23:05:45 -0300 |
|---|---|---|
| committer | dequis <dx@dxzone.com.ar> | 2015-08-27 23:05:45 -0300 |
| commit | aa3b61e178fbdb7069e171cc70c631ee63f72c8d (patch) | |
| tree | 11a5bcc921aa6f6e2121d7435d86a74b78002b64 | |
| parent | b6a3fbf3b94d1e7e7aee82375661fc0934fec48b (diff) | |
user-guide: add help for the jabber 'proxy' setting
| -rw-r--r-- | doc/user-guide/commands.xml | 20 |
1 files changed, 20 insertions, 0 deletions
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 @@ </description> </bitlbee-setting> + <bitlbee-setting name="proxy" type="string" scope="account"> + <default><local><auto></default> + + <description> + <para> + A list of <emphasis>file transfer proxies</emphasis> for jabber. This isn't the connection proxy. Sorry, look in bitlbee.conf for those. + </para> + + <para> + It's a semicolon-separated list of items that can be either <emphasis>JID,HOST,PORT</emphasis> or two special values, <emphasis><local></emphasis> (to try a direct connection first) and <emphasis><auto></emphasis> (to try to discover a proxy). For example, "<local>;proxy.somewhere.org,123.123.123.123,7777". + </para> + <para> + 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. + </para> + <para> + 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. + </para> + </description> + </bitlbee-setting> + <bitlbee-setting name="query_order" type="string" scope="global"> <default>lifo</default> <possible-values>lifo, fifo</possible-values> |