Topic: Is anyone running Jabber IM on 6B3 SME

[Bill Pflaumer]

Hello all,
I liked the Jabber IM contrib that ran on SME 5.12, but I don't believe the old contrib will function on the SME 6 Platform. Does anyone have it running on 6B3 ??

Bill

[Arno]

What is jammer
a instant message service?
whats the use on that on a linux dedicated svr?

[Michael Smith]

I liked the Jabber server contrib also ... v.nice ... but I could never find a SIMPLE (i.e. suitable for near-brainded users) client for use strictly on a LAN.  I don't know the answer to your question, though, Mr. Pflaumer ... perhaps the contrib developer will update it.

[Bill Pflaumer]

Did you go to jabber.org ?

Try http://www.jabber.org/user/clientlist.php


Bill

[Jon Blakely]

Ok guys, your wish is my command. When I get some spare time I will look at updating it. One of the major problems has been getting the transports to work as MS, Yahoo etc keep changing their protocols. I may look at doing one that just has Jabber and conference.

Jon

[Michael Smith]

Mr. P:  YES I tried MANY clients and while all of them worked, I really wanted something completely idiot-proof that would start up and automagically log the user into a common conference area.  Because if it ain't drop-dead easy it won't be used in the LAN (actually a WAN) and therefore won't be useful.

Any suggestions would be most appreciated, along with tales of working installations in LAN use (NO outside use desired, actually).

[Bill Pflaumer]

Jon
Thats sounds great. If I can help in anyway let me know. I have no problem being a Beta Site.

Bill

[Chris]

I would love to know when its supported on 6.Bill Pflaumer wrote:

[jb]

John,

I used your jabber howto to install under SME 6.0 final.  The instructions still seem to be valid.  I didn't have any problems running the install script and getting jabber installed.  The howto graphics are missing.

I used the server manager to enable the particular jabber services I wanted, used the jabber user panel to enable my users.  I used the exodus client as winjab is being deprecated for exodus.

I didn't try any of the transports.

Here are some things I see:

The jabber and jabberuser server manager panels show up in the unknown section.  I tried to look at this, but I don't know enough Perl nor know the format of how items are placed on the server manager screen.  If you can shed some light on this, I'd appreciate learning something.  

By default, users can (using Exodus - anyway), register any userid and password and gain access to the jabber server.  If you go to the server manager panel, the users defined on your system still show up as disabled, but they are actually enabled if they auto-registered.  Enabling and disabling the account is one way to then disable that user.  But, of course they could just register again via the client.  Also, userids that are not defined in your system, but have a registered jabber id, don't show anywhere.  These users have to be removed by going to /opt/jabber/spool/ and manually removing those ID's.  I tried changing 10jabber-reg to no to see if that would turn off the automatic registration, but that didn't work, so I removed the whole section all together, and that didn't work as well.  I did do a service jabber restart after all of my changes.  I started reading the jabber docs and will do more research in this area to see if I can find a way to not allow automatic registration.

Also by default it looks like server to server communication is enabled via 5269. I'd like to see this fragment further broken out.  One section for the 5222 stuff, and another for the 5269 stuff.  Or, you can take the view that someone can further beark up the templates to suit themselves.  If you do break them up, then an admin could remove the 5269 fragment.  That way it will give an admin the ability to enable this function if they want.  

That's just my 2 cents worth.  Hope some of this info helps.  I'd be glad to test anything that you put together.

Thanks for creating the howto,

JB

[rishi]

If you are still looking for fool proof Jabber clients try EXODUS for your windows clients. Once setup to login to the Jabber server it is fool proof. It will automatically log you in each boot and will automatically update its self from the web if you let it.

Have a look at:
http://exodus.jabberstudio.org/

Good Luck.

[jeroenm]

<cut>
The jabber and jabberuser server manager panels show up in the unknown section.  I tried to look at this, but I don't know enough Perl nor know the format of how items are placed on the server manager screen.  If you can shed some light on this, I'd appreciate learning something.  
<cut>

Doing a /sbin/e-smith/signal-event post-upgrade and a
/sbin/e-smith/signal-event reboot will fix this. There is probably a better way, this works for me.