On Thu, Jul 23, 2009 at 4:31 AM, Deds Castillod...@solutiongrove.com wrote:
Today I installed 0.6d2 from scratch. I noticed a few problems:
1. Basic ejabberd Configuration went smoothly. However, I got
stuck in Setup Shared Roster Groups for ejabberd. ejabberd is not
listening on port 5280:
On Thu, Jul 23, 2009 at 08:18:14AM +0200, Martin Langhoff wrote:
For xs0.6 you should _not_ configure ejabberd. I've posted the (much
simpler!) instructions for 0.6on this list about 2 months ago. Google
has excellent coverage of the archive ... ;-)
For future reference, it appears Martin was
On Thu, Jul 23, 2009 at 05:37:11PM +0800, Deds Castillo wrote:
On Thursday 23 July 2009, Joshua N Pritikin wrote:
On Thu, Jul 23, 2009 at 08:18:14AM +0200, Martin Langhoff wrote:
For xs0.6 you should _not_ configure ejabberd. I've posted the
(much simpler!) instructions for 0.6on this
On Thu, Jul 23, 2009 at 11:45 AM, Joshua N Pritikinjpriti...@pobox.com wrote:
If I understood Martin correctly, he is saying that nothing listening on
5280 is expected and correct behavior.
Correct :-) If for other reasons you want the web interface, then the
block in the config file is just
On Thursday 23 July 2009, Martin Langhoff wrote:
On Thu, Jul 23, 2009 at 11:45 AM, Joshua N
Pritikinjpriti...@pobox.com wrote:
If I understood Martin correctly, he is saying that nothing
listening on 5280 is expected and correct behavior.
Correct :-) If for other reasons you want the web
On Wed, Jul 22, 2009 at 02:24:05PM +0200, Martin Langhoff wrote:
Then I think around the time you looked at the instructions the
DNS configuration steps were all messed up.
Daniel Drake just did a major cleanup of that. Maybe it'd be a good
idea to retry from the start with the better
On Wed, Jul 22, 2009 at 9:12 AM, Joshua N Pritikin jpriti...@pobox.comwrote:
On Wed, Jul 22, 2009 at 02:24:05PM +0200, Martin Langhoff wrote:
Then I think around the time you looked at the instructions the
DNS configuration steps were all messed up.
Daniel Drake just did a major cleanup
On Thursday 23 July 2009, Joshua N Pritikin wrote:
On Wed, Jul 22, 2009 at 02:24:05PM +0200, Martin Langhoff wrote:
Then I think around the time you looked at the instructions the
DNS configuration steps were all messed up.
Daniel Drake just did a major cleanup of that. Maybe it'd be a