Thanks for fixing the transports - they do seem reliable now. Once this last issue is resolved are you able to remove the suggestions to get them fixed?
The transports should be (as everything is on the internet) fully qualified with a domain name. They do work as they are, but the transports display as ‘msn’ and ‘yahoo’ etc.
If you browse to one of my domains - say aurora.gen.nz - with a client that supports jabber browsing, you will see the transports listed as such:
The first two are correct. The JUD is pointing to the jabber.org one which is fine, and the conference one is fully qualified (I would prefer to be able to remove the ‘jabber’ from the middle but whatever)
In comparison, browse to any other Jabber server on the internet… here is syndicon.de as an example:
Notice how all the transports are fully qualified with the domain. This is important as if I wanted to (or indeed as I was required to when the dreamhost transports were broken) I could register with a syndicon.de transport. Now if my one was called ‘msn’ and the syndicon.de one was also called ‘msn’ my client would think that I was re-registering with the same transport, and promptly get confused.
Also, since previously the dreamhost transports were configured correctly, I have all my MSN users on my contact list as firstname.lastname@example.org. Now I have re-registered with the ‘new’ transports, it has re-added all my MSN contacts as ‘user%hotmail.com@msn’ so everything is duplicated. (Argh!)
I hope that answers the question. If not, let me know. I think it should be a simple configuration change to fix.