Hi Norman
Thanks a lot for that. But still not able to get it working. Am on my
wits end on this.
Running jabber on win environment. pymsnt and pyaimt are working fine.
pyyimt directory has xmpp and curphoo subdirectorys. am able to
trigger yahoo.py successfully and also the xmpp and curphoo
initiations..the compiled py files are created. that means jabber is
interacting succefully with pyyimt
mydomain.com is configured to the IP of the server directly.
Following log..it still indicates host-unknown
ThreadProcessXmppTransportConnection: Processing XMPP transport
connection from 202.134.186.109...
202.134.186.109: <?xml version='1.0'?><stream:stream xmlns="http://
jabberd.jabberstudio.org/ns/component/1.0" to="202.134.186.109"
version="1.0" xmlns:stream="
http://etherx.jabber.org/streams" >
202.134.186.109: <host-unknown/>
ThreadProcessXmppTransportConnection: Processing XMPP transport
connection from 202.134.186.109...
202.134.186.109: <?xml version='1.0'?><stream:stream xmlns="http://
jabberd.jabberstudio.org/ns/component/1.0" to="
mydomain.com"
version="1.0" xmlns:stream="
http://etherx.jabber.org/streams" >
202.134.186.109: <host-unknown/>
Also in the config.xml i have tried configuring
mydomain.com and the
IP as the server..still the issue remains.
Following is my config.xml:
<?xml version="1.0" ?>
<pyyimt>
<!-- This file contains options to be configured by the server
administrator. -->
<!-- Please read through all the options in this file -->
<!-- The JabberID of the transport -->
<jid>
yahoo.mydomain.com</jid>
<!-- The JabberID of the conference room handler. -->
<confjid>
chat.yahoo.mydomain.com</confjid>
<!-- The component JID of the transport. Unless you're doing
clustering, leave this alone -->
<!-- <compjid>yahoo1</compjid> -->
<!-- The public IP or DNS name of the machine the transport is
running on -->
<!-- This is used to select the outgoing IP address used to
connect to the Yahoo! network -->
<!-- otherwise known as the vanity address, it's safe to leave it
commented -->
<host>
mydomain.com</host>
<!-- The name of the transport in the service discovery list. -->
<discoName>Yahoo Transport</discoName>
<!-- The location of the spool file.. if relative, relative to the
PyYIMt dir. -->
<!-- Include the jid of the transport, if running multiple copies
of the same transport -->
<spoolFile>yahoouser.dbm</spoolFile>
<!-- The location of the PID file, relative to the PyYIMt
directory -->
<!-- Comment out if you do not want a PID file -->
<pid>PyYIMt.pid</pid>
<!-- The IP address or DNS name of the main Jabber server -->
<mainServer>
mydomain.com</mainServer>
<!-- The JID of the main Jabber server -->
<mainServerJID>
mydomain.com</mainServerJID>
<!-- The TCP port to connect to the Jabber server on (this is the
default for Jabberd2) -->
<port>5347</port>
<!-- The authentication token to use when connecting to the Jabber
server -->
<secret>XXXX</secret>
<!-- SASL username used to bind to Jabber server. -->
<!-- secret, above, is used for sasl password -->
<saslUsername>XXXX</saslUsername>
<!-- Allow users to register with this transport -->
<allowRegister/>
<!-- Allow users to use the Yahoo! chat rooms with this transport
-->
<enableChatrooms/>
<!-- Use external component binding. -->
<!-- This dodges the need to manually configure all jids that talk
to this transport. -->
<!-- Jabberd2 requires saslUsername and useRouteWrap for this to
work. -->
<!-- Wildfire as of 2.6.0 requires just this. -->
<!-- <useComponentBinding/> -->
<!-- Wrap stanzas in <route> stanza. -->
<!-- Jabberd2 requires this for useComponentBinding. -->
<!-- <useRouteWrap/> -->
<!-- You can choose which users you wish to have as
administrators. These users can perform some tasks with Ad-Hoc
commands that others cannot -->
<!--<admins>
<jid>admin@localhost</jid>
</admins>-->
<!-- The file to log to. Leave this disabled for stdout only -->
<debugFile>error.log</debugFile>
<!-- Show the raw data being sent and received from the xmpp and
yahoo servers -->
<dumpProtocol/>
</pyyimt>
Kinldy help me out
Vishal