SOCKS and Minger Server

SOCKS

SOCKS service is required for file transfers between XMPP/Jabber clients in cases where direct transfer is not possible due to NAT problems.

SOCKS server IP is described within the Service - Logging. It should contain the external IP address of your router or NAT device, i.e. the IP address that the Internet sees as you or your network.

Press the ":" button to have the IP address discovered for you.

Note: SOCKS Server port is set on the Properties tab of the Service dialog (System > Services > General tab, double-click the service). This port must be available on the machine this service will run on. The default port of 1080 may be already in use, if this is the case then you must locate a port that is free and enter it here. This port must also be enabled in your firewall/router.

Note: When using IceWarp SOCKS service together with PSI (IM client), it is necessary to set PSI properly file transfer to work correctly behind NAT: The Data transfer base port field (PSI > General- Options- Application) is to be set to 0 (zero). The Data Transfer Proxy field (PSI > General > Account Setup >(select account) > Modify > Misc. tab) has to include the JID value of the PSI > Service Discovery > Bytestreams Proxy item.

Note: If you are using NAT and your server does not recognize external IPs, specify the servers NAT IP in SOCKS properties (System > Services > double click SOCKS > SOCKS tab). If you are using load balancing, specify the master server's NAT IP.

Note: If you need to access SOCKS server from LAN and WAN and your public IP is not usable from LAN, you can put A DNS record to SOCKS IP field instead of IP. Then configure DNS, this record (domain name) to be translated into valid and accessible server IPs for both WAN and LAN. Note that Control and IM services need to be restarted and then a user needs to relog to WebClient to have the SOCKS IP change applied.

Minger Server

This technology allows you to use a complete domain sharing feature (including instant messaging, VoIP, etc.). You can have the same domain across multiple servers and keep different sets of accounts in each and still be able to reach the other accounts via email, instant messaging and VoIP.

There is a UDP server used for checking if a user exists on a remote server. This is protected by a domain shared (secret) password and it is processed by a smart hash mechanism (Minger Protocol RFC draft). You use the Minger functionality instead of using VRFY or RCPT domain.

Whenever a local account does not exist, remote servers (specified in the list) are checked simultaneously whether this account exists there. If yes, emails are forwarded there, IM messages are sent via S2S XMPP protocol and VoIP is also forwarded to the final destination.

Note: If you want to set a password that the servers serving the distributed domain will use for mutual contact, go to the Domains and Accounts > Management > {domain} > Options tab. This password has to be set on all these servers. This prevents queries from unknown servers. Also, the service comes stopped by default. Start it first to obtain any logs.