Hello Marcin
On 17.02.14 21:22, Marcin Mirosław wrote:
This isn't problem with resolver, (i'm pretty sure) this is problem
with udns. Udns-0.3 is buggy, please upgrade to 0.4. Please look at links:
http://www.corpit.ru/pipermail/udns/2014q1/000181.html
http://www.corpit.ru/pipermail/udns/2014q1/
Hello
I am running jabberd 2.3.1 on FreeBSD 9.1. After I did the
upgrade from Perl 5.12.5 to 5.16.3 (now with threads enabled) and
rebuild all ports depending on Perl (which includes jabberd), I
see the following behavior.
1) jabberd starts up just fine
2) I connect with my client and a few
Hello Guido
On 08.01.2014 21:01, Guido Winkelmann wrote:
On Monday 06 January 2014 22:06:32 Fabian Wenk wrote:
A friend also had the problem with his xabber client connecting
after he did upgrade jabberd from 2.2.17 to 2.3.1. After I have
just discussed this issue with him again (as I did not
Hello Tomasz
On 07.01.2014 00:29, Tomasz Sterna wrote:
Dnia 2014-01-06, pon o godzinie 22:06 +0100, Fabian Wenk pisze:
@Tomasz, could this be a "bug" or change from in jabberd 2.2.17
to 2.3.1?
In 2.3.0 GnuSASL >=1.1 dependency was introduced. So could there be an
incompatibility
Hello Guido
On 06.01.2014 21:00, Guido Winkelmann wrote:
For some reason, I cannot connect to jabberd2 2.3.1 with either xabber or
yaxim. I originally thought this was a xabber bug, so I reported it here:
https://github.com/redsolution/xabber-android/issues/268
However, it seems there are othe
Hello Joe
On 30.12.2013 00:44, Joe Malcolm wrote:
Anyone else running into a problem with 5222 & starttls for Adium? I'm
running jabberd2 2.2.17 on FreeBSD-10RC2.
I am using Adium 1.5.9 now (1.5.7 before) with jabberd-2.2.17_1
on FreeBSD 9.1 and it works.
Adium says:
17:47:20: (Libpurple:
Hello
On 23.04.2013 00:58, Fabian Wenk wrote:
On 22.04.2013 22:43, Tomasz Sterna wrote:
Looking at
https://github.com/jabberd2/jabberd2/blob/master/s2s/main.c#L137 it
should be possible to specify many local.origins.ip - in your case both
IPv4 and IPv6.
If I do understand it correctly
Hello Tomasz
On 22.04.2013 22:43, Tomasz Sterna wrote:
Dnia 2013-04-22, pon o godzinie 21:46 +0200, Fabian Wenk pisze:
Or would it be possible to change /
fix jabberd, that it does not need this IPv4 mapped IPv6
addresses any more?
Looking at
https://github.com/jabberd2/jabberd2/blob/master
Hello
I finally took the time to activate IPv6 in my jabberd (2.2.17)
installation. My systems are running with IPv6 since many years
and jabberd is one of the last services, which still was running
on IPv4 only. After many trial and errors I got it partly
running. When I did set :: instead o
Hello Marco
Hello Dejan
On 21.08.2012 00:41, Dejan Golja wrote:
when you find out how let me know :)
On Mon, Aug 20, 2012 at 9:19 PM, Marco Bertolaccini<121ma...@gmail.com>wrote:
i want to unsubscribe!
Just look into the headers of any e-mail from the mailing list,
and you will see th
Hello Auro
On 27.07.2012 02:17, Auro Tripathy wrote:
I have set up a jabberd2 test server at
'engdev1.remotewd2.com' and I'm now using the S2S component to
setup a chat session with my gmail account. Note, within my
domain, my test server does fine with chat sessions.
I get timeouts and I'm won
Hello Michael
On 12.04.2012 15:57, Michael Humphries-Dolnick wrote:
I'm noticing that in the last few weeks the website at
xiaoka.com is down. I also haven't seen any mail from this
list. Is there a plan to bring the site back up? If not, how
will updates to jabberd2 be distributed?
The mai
Hello Ismael
On 13.10.08 16:31, Ismael Olea wrote:
sx (ssl.c:762) couldn't load certificate from
/etc/pki/tls/private/tormento-jabber-cert.pem; error:0906D06C:PEM
routines:PEM_read_bio:no start line
Mon Oct 13 15:27:35 2008 [error] failed to load olea SSL pemfile
It looks like the .pem file is
13 matches
Mail list logo
