Thanks for the reply. This is strange that not so complex module like Jabber require much time to maintain for Zentyal developers. As I understant, it work separately from other Zentyal and linux modules. As I see, this module have only configuration page that generating config file, and "User jabber account" checkbox in User page.
Other parts of this module work separately: ejabberd server only get userlist from LDAP and generated by Zentyal config file. All other works independently.
So for update module to new version we must only track ldap query changes and Zentyal API for adding elements in interface.
I'm not good specialist in Perl, but will try to fork Zentyal git and port Jabber module for Zentyal 4.1 by myself, this is easier for our company that changing Zentyal to some other solution. If something happens with my port, I submit pull request to you.
Because removing Jabber support for Zentyal broke good way of IM communication for clients, and not provide any replacement. Let's use Facebook, Skype, Telergram, Viber for corporate talking?
No, let's restore Jabber support, good opensource solution for corporate IM.