Date: Fri, 07 Nov 2008 21:30:14 -0600 From: Steven Susbauer <stupendoussteve@hotmail.com> To: Da Rock <rock_on_the_web@comcen.com.au> Cc: freebsd-questions@freebsd.org Subject: Re: Messenger servers Message-ID: <491507C6.7040509@hotmail.com> In-Reply-To: <1226111879.1220.9.camel@laptop1.herveybayaustralia.com.au> References: <1226111879.1220.9.camel@laptop1.herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC3469F650E872800A2AC95A1 Content-Type: multipart/mixed; boundary="------------020801080700000003080407" This is a multi-part message in MIME format. --------------020801080700000003080407 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Da Rock wrote: > I haven't checked the list for around a week- I'm still catching up! :)= >=20 > I'm trying to sort out a messenger server for work purposes, and > although I've found a few I'm hoping some input from sysadmins who have= > deployed these might help our decision. I've found Gale, Jabberd2, > OpenFire, and SJECS (Sun Java Communication Suite). >=20 > Our requirements are for collaboration (multiple users simultaneous > chatting together- with audio/video if possible), realtime audio/video > (with a preference for audio; ergo video can go to the dogs to maintain= > audio quality, although a means to adjust this- on the fly if possible-= > would be useful), and chat. >=20 > Tall order, eh? Ease of admin would be good, but my main concern is > stability and reliability (I'll make up a software solution to > administrate if needs be). >=20 > Thanks guys. >=20 I would avoid OpenFire, some pretty gnarly vulnerabilities were announced today, and the vendor doesn't seem to be in a hurry to fix them= =2E http://www.andreas-kurtz.de/advisories/AKADV2008-001-v1.0.txt Good luck! -Steve --------------020801080700000003080407 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="signature.asc" LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0KVmVyc2lvbjogR251UEcgdjIuMC45IChH TlUvTGludXgpCkNvbW1lbnQ6IFVzaW5nIEdudVBHIHdpdGggTW96aWxsYSAtIGh0dHA6Ly9l bmlnbWFpbC5tb3pkZXYub3JnCgppRVlFQVJFQ0FBWUZBa2tWQjJRQUNna1EyaTNZWXpiRHQw K0x0d0NmVTQrTEx5SjJSRGN1VG53YnVYQjZQUlhnClJEb0FvTXpLUlp2TzkwOXNiTk9IWHJo Z0djLzVRTm5sCj04ODE2Ci0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQoK --------------020801080700000003080407-- --------------enigC3469F650E872800A2AC95A1 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkkVB8YACgkQ2i3YYzbDt09kzwCfVMMfX2ram+OZe0XtpMkskd6f /5MAmQHtGtTXRkW4Y83sjYkSBQwzUxyF =J/PP -----END PGP SIGNATURE----- --------------enigC3469F650E872800A2AC95A1--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?491507C6.7040509>