Ajcody-Instant-Messaging-Topics: Difference between revisions
Line 14: | Line 14: | ||
* [NEW] Remove IM server | * [NEW] Remove IM server | ||
** "ZCS 7.0 should not include an IM server." | |||
** http://bugzilla.zimbra.com/show_bug.cgi?id=45932 | ** http://bugzilla.zimbra.com/show_bug.cgi?id=45932 | ||
* IM GA (no ISP/HSP) | * IM GA (no ISP/HSP) |
Revision as of 01:36, 6 April 2010
- This article is NOT official Zimbra documentation. It is a user contribution and may include unsupported customizations, references, suggestions, or information. |
IM - Instant Messaging
Actual Instant Messaging Topics Homepage
Please see Ajcody-Instant-Messaging-Topics
When Will IM Be Out Of Beta - Update
Please track the following bug:
- [NEW] Remove IM server
- "ZCS 7.0 should not include an IM server."
- http://bugzilla.zimbra.com/show_bug.cgi?id=45932
- IM GA (no ISP/HSP)
Performance Issues Caused By IM [BETA]
Please note, that this bug has had a significant enough impact on performance of production servers that we recommend not running IM [BETA] if you have no significant reason to do so.
- "IM service connection leak,memory leak"
To turn off IM:
zmprov -l -v mcf full zimbraXMPPEnabled FALSE
And then you'll need to start and start zimbra:
zmcontrol stop zmcontrol start
Enabling IM [BETA] - 5+ ZCS Server
Check to see if it's enabled:
zmprov gacf zimbraXMPPEnabled
If it returns FALSE, you'll need to set it as TRUE:
zmprov -l -v mcf full zimbraXMPPEnabled TRUE
Now to enable via the COS's for the users. I'll assume you are using the COS called "default" for your domain below - change it if your using another COS for the variables below.
Check to see what current status is:
zmprov gc default zimbraFeatureIMEnabled zmprov gc default zimbraFeatureInstantNotify
If they return FALSE, set them to TRUE.
zmprov -v mc default zimbraFeatureIMEnabled TRUE zmprov -v mc default zimbraFeatureInstantNotify TRUE
And then you'll need to stop and start zimbra:
zmcontrol stop zmcontrol start
What Happen to AOL IM and MSN?
From the 5.x Release Notes:
- Note: Update about Instant Messaging feature - In order to ensure the scalability of our server software and provide a quality experience to our customers, we have removed IM interoperability with AOL and MSN that was present in previous 5.0.0 beta releases. This functionality may be restored in a future release.
3rd Party Client Setup Up Examples
Please see:
Additional information on those clients can also be found here:
Ajcody-Notes#IM_-_Instant_Messaging_Clients
Addresses things like group chat /conference rooms and so forth.
ZCS to ZCS IM Availability
Please review the following bug and note the DNS SRV entries I posted within it.
- "ZCS to ZCS IM issues."
Integration With External IM Servers
Please see:
- "Integration with external IM servers (XMPP proxy support)"
IM And Legal Intercept And Archiving
Please see:
- "Legal intercept support: IM"
- "Other collaboration data (IM, Docs, Calendars) need to be archived"
- "RFE: Saving IM history from external IM clients"
This might also be relevant:
- "Regulatory Compliance - code to them and achieve the ability to verify in our documentation"
IM - Conference Rooms
Please see the RFE I made:
- "IM : conference room admin settings"
Also the bug/RFE about Conference rooms in Multi-Server Configurations
- "IM Conference Rooms Don't Work in Multi-Server Setup"
Embedded IM Requests To Join Chat Session In Html/Email
Formats are (I think, still investigating this):
- Jabber/XMPP
- YahooIM
- ymsgr: or yim: (not sure if both work or not)
- AOL IM
- aim:
- MSN
- msnim: or msn: (not sure if both work or not)
You'll need to configure your OS to handle the protocol when called to, so that it launches the correct application.
Resource
- Great resource about this topic and how to adjust your OS to handle the different IM url's.
Related Bugs & RFE's
- "ZWC to handle differnt IM url's - option to set ZWC IM client or external client by OS"
- "Allow Calendar Events in ZWC to handle IM url calls"
Buddy Notification In ZWC
Please see:
- "Buddy notifications support for IM presense"
Other General Bugs & RFE's
Please see:
- "Unable to delete IM Buddy whos account has been renamed"
- "Ability to "restart" IM service without a full mailboxd restart required"
IM And DNS SRV Records
Show ports are in use:
[root@mail3 ~]# lsof -P -n -i :5222 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME java 5869 zimbra 143u IPv6 6530439 TCP *:5222 (LISTEN) [root@mail3 ~]# lsof -P -n -i :5269 COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME java 5869 zimbra 144u IPv6 6530440 TCP *:5269 (LISTEN) [root@mail3 ~]# lsof -P -n -i :5269
An example of what I've added to my internal DNS/BIND zone record:
$ttl 38400 zimbra.DOMAIN.com. IN SOA zimbra.DOMAIN.com. ajcody.zimbra.DOMAIN.com. ( 1207910051 10800 3600 604800 38400 ) IN NS mail3.zimbra.DOMAIN.com. zimbra.DOMAIN.com. IN MX 10 mail3.zimbra.DOMAIN.com. _xmpp-client._tcp.zimbra.DOMAIN.com. SRV 5 0 5222 mail3.zimbra.DOMAIN.com. _xmpp-server._tcp.zimbra.DOMAIN.com SRV 5 0 5269 mail3.zimbra.DOMAIN.com. _jabber._tcp.zimbra.DOMAIN.com. SRV 5 0 5269 mail3.zimbra.DOMAIN.com. mail3 IN A 192.168.0.16
The _jabber._tcp if for backward compatibility for older servers and shouldn't be necessary.