https://www.ejabberd.im/node/3630 en https://www.ejabberd.im/node/3630#comment-55100 <p>You can use an acl with resource_regexp. Then hard code your client and recompile with the permited Resource and don't tell anybody that Resource. Then create an acl for Ejabberd (version &gt;= 2.1.1) like this:</p> <p>{acl, xxxxxx, {resource_regexp, "myresource"}}.</p> <p>{access, c2s, [{deny, blocked},<br /> {allow, xxxxxx}]}.</p> Thu, 07 Jan 2010 12:18:29 +0000 gersonsm comment 55100 at https://www.ejabberd.im https://www.ejabberd.im/node/3630#comment-54576 <p>That feature isn't implemented in ejabberd. By the way, clients can fake their software version, see <noindex><a href="http://coccinella.im/bypassing-openfire-client-control" rel="nofollow" >A Fool's Guide to Bypass Openfire's Client Control</a></noindex>.</p> <p>Another solution would be to use the server listening port as a way to enforce users to 'update' their clients. By default clients and ejabberd use port 5222. You can start an additional listener on port 18910 for example. Put that port as default in your custom client. Tell users to update. After a few days, close the port 5222. Only the users that updated their client, or that configured that custom port in their client, will be able to login.</p> <p>With the next client update you can repeat, with a different port.</p> Mon, 24 Aug 2009 14:35:02 +0000 mfoss comment 54576 at https://www.ejabberd.im