Instant Messaging in Kerio Connect
Kerio Connect mail server recently added Instant Messaging support. When I first heard that, I thought it was absolutely rediculous! If you want IM, open up the ports in your firewall and let it go.. why on earth do you need the mail server involved? I'm not generally a big fan of IM anyway, so I just dismissed this idea entirely.
Not so fast
I was wrong. Actually, there are some real benefits to passing IM through the mail server.
The first is that, by default, the only people who can use IM are those who are in your mail domain(s). You aren't opening up IM so that Bill can waste away the day chatting about sports with his friends. Moreover, if you don't want Bill to use this at all, you can assign a policy that prevents him from using IM. Or, you can make a default policy that prohibits IM to everyone and add an IM allowed policy for specific users.
If you really want IM open to the world, you can do that (see Configuring instant messaging in Kerio Connect in the Kerio Knowledge Base).
If you only want this within your domain and aren't going to restrict anyone, there's nothing to do at the server: it's ready to work - it's in Services and is running by default.
As most IM clients now support such things as video, file sharing, screen sharing and group chat, you also have all that available - again, for the people you choose only.
Of course, IM is also a way to see if someone is available without bothering them with a phone call.
Although I'm a very small organization, I can see using this myself to get a quick message to my wife when I am out of the office. As long as I have Internet access, I can use IM to reach her and she can reach me - without having opened up IM access to the world at large!
So, I was wrong. I can see where this feature would actually be very useful in many organizations. Check out more at Kerio Connect Instant Messaging.
You need a client that understands XMMP. Mac Messages and iChat are both fine, as are many third party clients. On Windows, Pidgin is free and works fine. I'll use that as an example.
After downloading and installing, run Pidgin. It will ask you to add an account.
Choose XMMP as the account type. If you are configuring a client that doesn't offer that, look for "Jabber". What you need is the ability to point it at your Connect server.
Fill in your account name and domain as shown here. On some clients, that would be one line: [email protected], for example. For Pidgin, they are separate.
Finally, set the desired encryption and the DNS name (or IP) of your server on the Advanced tab. That's it - you should now be able to enable the account and start chatting.
Here's Monal for iPad - simple setup, just say it's a Jabber server.
Here's a setup for PSI that a customer sent.
Here are some other screenshots he sent along:
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\bruggles.CO>nslookup -querytype=SRV _xmpp-client._tcp.co.grafton.nh.us Server: UnKnown Address: 10.0.0.1 Non-authoritative answer: _xmpp-client._tcp.co.grafton.nh.us SRV service location: priority = 0 weight = 5 port = 5222 svr hostname = mx01.co.grafton.nh.us C:\Users\bruggles.CO>nslookup -querytype=SRV _xmpp-server._tcp.co.grafton.nh.us Server: UnKnown Address: 10.0.0.1 Non-authoritative answer: _xmpp-server._tcp.co.grafton.nh.us SRV service location: priority = 0 weight = 5 port = 5269 svr hostname = mx01.co.grafton.nh.us C:\Users\bruggles.CO
Windows DNS SRV Records for Kerio IM
Kerio IM External DNS A Records
Windows DNS XMPP CLIENT RECORD
Windows DNS XMPP SERVER RECORD
With the Proper XMPP Records in Place, I was able to
uncheck Manually Specify Server Host Port and (like magic) it found the server
Got something to add? Send me email.
(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version
Increase ad revenue 50-250% with Ezoic