I think that I understand what Josh wants and it is exactly what I am looking for.
Here is the scenario
I have set up a jabber server inside of my organization and we have a significant # of users logged in using the system. All is good here.
I would like to put a second server up in my DMZ, which would be accessible to the Internet for remote employees to use (only when working remotely) that they could attach to. I would then configure some ACL’'s between the two hosts so that they could communicate to the internal server. Also, I would disallow inband account creation and so forth on the external server.
This would alllow remote employees to logon to the outside jive server and make a connection to the inside users on the inside.jive server without having to have 2 independent accounts and separate rosters.
My primary goal is to keep all instant messaging to remote employees and internal employees directly on our own instant messenging servers (rather than allowing AIM, ICQ or some other centralized server to get in the mix). However, i don’‘t want to make our internal jive server open to the internet and I don’'t want to allow non-employees to create accounts on the outside jive server.
At the present time, employees have to make a VPN connection to the network and then just run the client of their choice to connect to our internal jive server.