2005-12-28 07:27:48 +01:00
|
|
|
===========================================================================
|
2006-04-16 05:27:05 +02:00
|
|
|
$NetBSD: MESSAGE,v 1.3 2006/04/16 03:27:05 schnoebe Exp $
|
2005-12-28 07:27:48 +01:00
|
|
|
|
2006-04-16 05:27:05 +02:00
|
|
|
You will need to customize the following file to get pyaimt to work
|
2005-12-28 07:27:48 +01:00
|
|
|
with jabber:
|
|
|
|
|
|
|
|
|
|
${PKG_SYSCONFDIR}/pyaimt.xml
|
|
|
|
|
|
|
|
|
|
Quick start for jabberd2:
|
|
|
|
|
|
|
|
|
|
Verify and update the following fields in
|
|
|
|
|
${PKG_SYSCONFDIR}/pyaimt.xml:
|
|
|
|
|
|
|
|
|
|
<jid>...</jid> -- Set to the public name of the service
|
|
|
|
|
ex: aim.jabber.example
|
|
|
|
|
<mainServer>...</mainServer>
|
|
|
|
|
-- Set to the hostname or IP address
|
|
|
|
|
of the main jabber server
|
|
|
|
|
<mainServerJID>...</mainServerJID>
|
|
|
|
|
-- Set to the JID (jabber ID)
|
|
|
|
|
of the main jabber server
|
|
|
|
|
<secret>...</secret> -- should be set to the legacy components
|
|
|
|
|
shared secret in jabber2's router.xml
|
|
|
|
|
(look for <secret>...</secret> in
|
|
|
|
|
router.xml)
|
|
|
|
|
|
2005-12-28 07:28:37 +01:00
|
|
|
Additionally, you can use the SASL authentication mechanisms and jabberd2's
|
2005-12-28 07:27:48 +01:00
|
|
|
component protocol extensions by updating the following two fields:
|
|
|
|
|
|
|
|
|
|
Uncomment <useJ2Compoent/>
|
|
|
|
|
set <saslUsername>...</saslUsername> to a user defined in
|
|
|
|
|
jabber2's router-users.xml
|
|
|
|
|
|
|
|
|
|
===========================================================================
|
