Dan VerWeire

@lipanski's branch https://github.com/lipanski/dav/commit/4bddb8b478948556a14b3f80f73711f366ce92b8 appears to work with SOGo at first glance.

If I create a working solution I will definitely submit a PR.

I'm not a ruby expert either, but I did trace the code best I could and it seems like parse is ultimately not called at all if `dns_status` is not...

This is the patch that I have in place on some older version (2595481b266199d8e29347dea2764f2c10202805) before 2.0. I didn't even realize 2.0 was out! I haven't had any tracking issues since...

Either change the port on which node-discover is running: port-cluster1.js ```js var Discover = require('node-discover'); var cluster1 = Discover({ port : 12345 }); ``` port-cluster2.js ```js var Discover = require('node-discover');...

Good catch on two bugs. To prevent the undefined array in networks.js, we should declare `self.destination = [];` around line 45. https://github.com/wankdanker/node-discover/blob/master/lib/network.js#L45 There is prevention code to prevent multiple calls...

Has this worked for you in a previous version of object-mapper?

Hey @my2b. Thank you for your contribution. This looks pretty good. The only difference that I would like to see is to only execute the block of code that determines...

Hi @my2b! Just make the changes in your local git repo, commit them and then push them to your master branch on github. That will update this pull request. No...

There is not an option to configure that at the moment. :(