Feedback from upstream. The first and second call is because of
resolver routines. The 3. connection is the "libstrophe"
connection.
When I understood well, the reason of the bugs was a wrong IPv6
configuration. After failed IPv6 connection, libstrophe didn't
try IPv4 as fallback. Am I right?
Thanks for the update, the functionality seems better but strange. It
connects to both addresses and closes then, and then makes a third connection
to do the actual work.
I think the correct functionality is to connect to each address in turn and
use the first one that works. Below is an
2 matches
Mail list logo
