How to install pymsnt (msn transport) on 10.5 server

Question

Here are the basics for installing pymsnt on an 10.5.x (leopard) server that already has ichat services running. There is an assumption that the reader has a reasonable understanding of using a terminal and understands the basics of Linux.
Most of what you need is already installed on the 10.5 server as part of the advance installation. You also need to ensure that the Developer tools are installed.
We are going to install our packages here: /Library/Python/2.5/site-packages so log on as an admin user and change to this directory.
*cd /Library/Python/2.5/site-packages/*
Now we need to install two packages that are needed. They are pycrypto and pyopenssl. As at time of writing these can be obtained from the links below. Normally the curl command will fetch them.
*curl -O http://www.amk.ca/files/python/crypto/pycrypto-2.0.1.tar.gz*
*curl -O http://puzzle.dl.sourceforge.net/sourceforge/pyopenssl/pyOpenSSL-0.6.tar.gz*
We also need the latest version of pymsnt.
*curl -O http://delx.cjb.net/pymsnt/tarballs/pymsnt-0.11.2.tar.gz*
Now lets untar the packages.
*tar xvfz pyOpenSSL-0.6.tar.gz*
*tar xvfz pycrypto-2.0.1.tar.gz*
*tar xvfz pymsnt-0.11.2.tar.gz*
Next set up the pycrypto package.
*cd pycrypto-2.0.1*
*python setup.py build* - don't worry too much about the warning errors
*python setup.py install* - last line should look something like: Writing /Library/Python/2.5/site-packages/pycrypto-2.0.1-py2.5.egg-info)
and to test the installation:
*python test.py*
Next set up the pyopenssl package
*cd ../pyOpenSSL-0.6*
*python setup.py build* - don't worry too much about the warning errors
*python setup.py install* - last line should look something like: Writing /Library/Python/2.5/site-packages/pyOpenSSL-0.6-py2.5.egg-info
now lets get to the basics of setting up the pymsnt package. Start by giving the directory a sensible name.
*cd ..*
*mv pymsnt-0.11.2 pymsnt*
and cleaning up the package downloads
*rm .gz
For some reason the Apple have not installed the twisted web module in the normal directory. However a copy exists elsewhere on the server. I’m not sure why they have done it this way. The easiest way to fix this is to make a copy in the normal way.
*sudo cp -R /usr/share/caldavd/lib/python/twisted/web/ /System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/twis ted/web*
Next set up the config.xml file that pymsnt uses when it starts up. An example exists in the pymsnt directory so make a copy
*cp pymnst/config_example.xml pymsnt/config.xml*
Next using your favourite text editor make the following changes.
<jid>msn</jid> change to <jid>msn.*[server]*</jid> Where server is the name you give to your ichat server in the server admin application. Note that you also need a FQDN for for the jid
*<!-- <discoName>MSN Transport</discoName> -->* remove the *<!-- and -->*
*<!-- <spooldir>/path/to/data</spooldir> -->* change to <spooldir>/var/jabberd/spool</spooldir>
<background/> change to *<!-- <background/> -->* This is necessary if you are wanting to use the launchd services to keep the service running.
*<!-- <reactor>poll</reactor> -->* change to <reactor>default</reactor>
<secret>secret</secret> change to same settings found in file c2s.xlm (private/etc/jabberd)
*<!-- <debugLevel>0</debugLevel> -->* change to <debugLevel>2</debugLevel>
*<!-- <debugFile>debug.log</debugFile> -->* to <debugFile>pymsnt.log</debugFile>
and save the file.
Almost there…. now edit private/etc/jabberd/router-users.xml and add the following
<user>
<name>msn.*[server]*</name>
<secret>+[as existing entry in file]+</secret>
</user>
Where [server] is as previous setting in config.xml file.
Save the file (no need to restart ichat).
Now time to start I the pymsnt module
Ensure your currect directory is correct
*cd /Library/Python/2.5/site-packages/pymsnt/*
now run the package:
*sudo ./pymsnt.py &*
You should see a warning message about using default reactors and about not having installed Python Image Library (unless you have installed it).
Using a jabber client that support service discovery (not iChat) you should be able to see the msn transport listed under msn.[server]. Remember you need a FQDN entry for this to work.
Good luck.

Answer 1

Also should have noted that after rebooting system, jabberd will no longer run, not sure if you can point me in the right direction to fix this as well.
Mar 10 23:44:56 maccoyltonserver jabberd/c2s[35396]: starting up
Mar 10 23:44:56 maccoyltonserver jabberd/c2s[35396]: initialised auth module 'sqlite'
Mar 10 23:44:56 maccoyltonserver jabberd/router[35392]: [127.0.0.1, port=50738] connect
Mar 10 23:44:56 maccoyltonserver jabberd/router[35392]: [127.0.0.1, port=50739] connect
Mar 10 23:44:56 maccoyltonserver jabberd/c2s[35396]: [maccoyltonserver.homeip.net] configured; realm=(null)
Mar 10 23:44:56 maccoyltonserver jabberd/c2s[35396]: attempting connection to router at 127.0.0.1, port=5347
Mar 10 23:44:56 maccoyltonserver jabberd/router[35392]: [127.0.0.1, port=50740] connect
Mar 10 23:44:56 maccoyltonserver jabberd/router[35392]: [127.0.0.1, port=50741] connect
Mar 10 23:44:56 maccoyltonserver jabberd/router[35392]: [127.0.0.1, port=50740] authenticated as conference.maccoyltonserver.homeip.net
Mar 10 23:44:56 maccoyltonserver jabberd/router[35392]: [conference.maccoyltonserver.homeip.net] online (bound to 127.0.0.1, port 50740)
Mar 10 23:44:56 maccoyltonserver jabberd/router[35392]: no secret in database
Mar 10 23:44:56 maccoyltonserver jabberd/sm[35394]: error from router: Authentication failed ((null))
Mar 10 23:44:56 maccoyltonserver jabberd/sm[35394]: connection to router closed
Mar 10 23:44:56 maccoyltonserver jabberd/sm[35394]: attempting reconnect (3 left)
Mar 10 23:44:56 maccoyltonserver jabberd/router[35392]: no secret in database
Mar 10 23:44:56 maccoyltonserver jabberd/resolver[35393]: error from router: Authentication failed ((null))
Mar 10 23:44:56 maccoyltonserver jabberd/resolver[35393]: connection to router closed
Mar 10 23:44:56 maccoyltonserver jabberd/resolver[35393]: attempting reconnect (3 left)
i guess it serves me right .. it's been rock solid since I installed the server a couple of months back, maybe this pymsnt is a bad idea.
Dave