Ok, I took a step back - seems there is more than one problem (not only s2s, but more probs with jabber.org accounts).
So I set up a second server (server2.mydomain.com). I logged in with a user on that server and tried to add a test1@mydomain.com to the roster. The user is then shown as “pending” in the roster.
I am logged in as test1@mydomain.com with another client. As soon as this user is added to the other user’s roster, I get a popup which asks me if I want to allow this and if I want to add the other user to my roster. However, for the user on the second server, the status of the roster entry for the added user is still “pending”, and there is no popup asking if I want to allow being added by the other user.
On my primary server, I get the following error message:
2007.11.08 15:43:33 Creating a DirContext in LdapManager.getContext()…
2007.11.08 15:43:33 Created hashtable with context values, attempting to create context…
2007.11.08 15:43:33 … context created successfully, returning.
2007.11.08 15:43:33 Creating a DirContext in LdapManager.getContext()…
2007.11.08 15:43:33 Created hashtable with context values, attempting to create context…
2007.11.08 15:43:33 … context created successfully, returning.
2007.11.08 15:43:33 Failed to route packet to JID: test@server2.mydomain.com packet:
<presence id=“He8iy-232” to="test@server2.mydomain.com" type=“subscribe” from="test1@mydomain.com/spark"/>
2007.11.08 15:43:33 Failed to route packet to JID: test@server2.mydomain.com packet:
<presence id=“He8iy-233” to="test@server2.mydomain.com" type=“subscribed” from="test1@mydomain.com/spark"/>
2007.11.08 15:43:33 Failed to route packet to JID: test@server2.mydomain.com packet:
<presence id=“He8iy-156” from="test1@mydomain.com/spark" to="test@server2.mydomain.com">
<status>Available</status>
<priority>1</priority>
</presence>
I then changed the domain on my primary from mydomain.com to server1.mydomain.com - I did not use our domain name, but the actual name of the server.
Now every thing works fine: as soon as I allow being added to the roster, the other user also gets a popup asking to confirm this, and thn the status changes from pending to the actual status of the user.
So it seems I have a problem with using our domain instead of the real host name. However, I would have expected the other server to show me a warning, not the one with the problem/changed domain.
As stated obove, I think I configured the IN SRV entries correctly. dig returns the hostname of my jabber server when I ask for jabber.tcp.mydomain.com
$ dig @nameserver jabber.tcp.mydomain.com any +short
0 0 5269 jabber.mydomain.com.
$ dig @nameserver xmpp-server.tcp.mydomain.com any +short
0 0 5269 jabber.mydomain.com.
$ dig @nameserver xmpp-client.tcp.mydomain.com any +short
0 0 5222 jabber.mydomain.com.
Thanks!