s2s does not handle SSL errors properly

[Simon]

It's not actually possible to set the verify mode... because the config never reads it, but when it's set this happens:

06 20:21:42 jabberd/resolver[12516]: [_xmpp-server._tcp.twitter.com] resolved to 128.121.145.166:5269 (60 seconds to live)
06 20:21:42 jabberd/resolver[12516]: [_xmpp-server._tcp.twitter.com] resolved to 128.121.145.166:5269 (60 seconds to live)
06 20:21:42 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] outgoing connection
06 20:21:43 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] error: SSL handshake error (error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed)
06 20:22:17 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:22:22 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:22:27 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:22:32 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:22:37 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:22:42 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:22:47 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:22:52 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:22:57 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:02 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:07 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:12 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:17 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:22 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:27 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:32 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:37 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:42 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:47 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:52 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:23:57 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:24:02 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:24:07 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:24:12 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:24:17 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out
06 20:24:22 jabberd/s2s[12521]: [7] [128.121.145.166, port=5269] connection to twitter.com timed out

[Simon]

Doing sx_kill() and returning -1 in the event_ERROR case seems to fix this...

[smoku]

In [576]: Merged asynchronous domain resolving in s2s component support by Simon Arlott. Closes #206 #208 #216