Setting up a XMPP/Jabber Client (Psi)

IceWarp Server's IM Server will accept connections from any XMPP/Jabber-enabled clients.

You can find a list of XMPP/Jabber-enabled clients at http://www.www.jabber.org/user/clientlist.php.

This section shows you how to set up a client, using Psi, as an example.

Latest version of Psi can be downloaded from the Psi website ? http://www.psi-im.org/.

Tip: There is a portable version of PSI available to skip any installation.

Note: If your server uses AD authorization, you must set your IM client to use plain text authentication only.

For clients that do not allow this kind of authentication, IceWarp Server synchronizes passwords with the appropriate AD account so that it is possible to use challenge-response authentication.

If the user can not log in, there are two possibilities:

  1. To log into any other IceWarp Server service that uses plain text authentication (for example WebClient, Outlook), so that the password will be synchronized to IceWarp Server. Then the challenge-response authentication in the Jabber client will work until the next password change. After password change, it is necessary to repeat this step.
  2. Administrator has to force plain authentication to IM client. In System - Advanced - Protocol, Check the PLAIN box and un-Check all other boxes in this section.

    Note: Be aware of the fact that this setting means that when the SSL connection is not used, all passwords are sent without encrypting.

    User has to set the client to use (allow) plain text authentication (see the First Run of Psi section).

    Note: "allow" means that this type of authentication is possible but NOT forced in all cases.

In case you want to use PSI together with IceWarp SOCKS service, it is necessary to set PSI properly, otherwise file transfers could be problematic. For detailed information, refer to the System Node - Services - General ? SOCKS and Minger Server chapter.