Well due to a report of spam coming from my xmpp server with randomly generated and deleted accounts I’ve disabled in-band registration. I’m going to start working on a web page so people can register new accounts without the risk of spammers creating accounts but in the mean time there is no way to create a new xmpp (jabber) account at bgmn.net. Sorry for the inconvience.
Dynamic DNS allows you to update a known host name whenever your IP changes. For more information take a look at the excellent (and free) service at DynDns or RFC 2136. With dynamic dns, whenever the computer recieves a new IP address it will send out an update to the DNS server pointing a known name (such as office.example.org) to the new IP address automatically. This allows you to connect to your computer at home just like any other server on the internet without having to know the IP.
Looks like the upgrade to Openfire 3.6.0a didn’t go as planned. Something in the database upgrade between versions messed up and the entire database had to be scrapped… Unfortunatly this means you’re once again going to have to register with the server, register with the transports and recreate your rosters (though all your buddies from AOL/MSN/Yahoo should be automatically readded when you register). Sorry everybody I know this is a PITA!
I did a little bit of research since my last post and determined that ideally I should only be offering one certificate, not both RSA and DSA. So since the RSA cert is signed by the Jabber Foundation (accepted in more clients/servers than the cacert.org cert) I think I’m going to remove the DSA cert comepletely. Let me know if this turns out to cause any problems and I’ll add it back in.
I don’t think this will really affect anybody since most of you already seem to be connected via SSL but bgmn.net will now require clients to be connect via SSL. I did change the certificate (at least the RSA one, the DSA cert is still signed by cacert.org, does anybody know if you really need both?) with one signed by the Jabber Foundation (startcom cert) so it should be supported by most clients out of the box.
If there are any problems with this change let me know.
As of now, jabber service should be restored on the bgmn.net server. As I mentioned in the last post you will have to re-register and the IM gateway is now limited to local users. If you notice any S2S problems I just added the DNS records again so it might take a while for it to propigate. Let me know if you have any issues.
Sorry for the downtime everybody, I’m working as quickly as my free time allows to get this server back up and running. I should have the jabber service up by tonight however all user account information has been lost so unfortunatly you’ll have to signup again.
This time around I’m removing the pyaim/pymsn transports and going with the native openfire gateway. I’m making this change mainly because I never found time to look for/fix that memory leak and having to manually keep an eye on and restart those services was a PITA.
What does this mean for you?
Mainly that you’ll still be able to use this server and transports for connecting to AIM/MSN however your account will have to be based on this server (JID ending with @bgmn.net). All you should have to do is create another account once I start the server again. Sorry to all the google talk users! I know there was a lot of you out there but maybe push AOL to actually connect to the Jabber network. I know AOL was playing around with XMPP but I don’t know if that’s gone anywhere
Also since I’ve lost all the account/roster information you’re buddy list will have to be recreated.
Again everybody sorry for any inconvience but the hard drive failed and I of course had no viable recent backups. I’ll post again once the jabber server is setup.