<div dir="auto">This is super useful. Thanks!</div> <div class="gmail_quote"><div dir="ltr" class="gmail_attr">Op za 28 mrt. 2020 19:58 schreef Kim Alvefur <<a href="mailto:zash@zash.se">zash@zash.se</a>>: </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello! Server-to-server connectivity is not perfect today. Certificates expire, mistakes are made in DNS zones and firewall configurations. In order to see how XMPP software react to such things without having to wait for problems to pop up, I have set up a few test cases. Most of these have some sort of configuration problem, ranging from faulty DNS and blocked ports up to certificate problems and XMPP s2s authentication. I would be happy if this leads to improved error reporting all the way to end users. Some hint about why their messages could not be delivered are surely better than having them disappear into the void without a trace. Logging and reporting for service operators is also important. Website with list of test cases: <<a href="http://badxmpp.eu/" rel="noreferrer noreferrer" target="_blank">http://badxmpp.eu/</a>> Test cases can also be listed via XEP-0030 items request: <xmpp:<a href="http://badxmpp.eu?disco;type=get;request=items" rel="noreferrer noreferrer" target="_blank">badxmpp.eu?disco;type=get;request=items</a>> Suggestions for additional tests are welcomed. Equivalent tests for XMPP client connectivity is one thing I would like to add, but as a server developer I choose to focus on s2s first. -- Happy testing, Kim "Zash" Alvefur Prosody developer XMPP Council _______________________________________________ JDev mailing list Info: <a href="https://mail.jabber.org/mailman/listinfo/jdev" rel="noreferrer noreferrer" target="_blank">https://mail.jabber.org/mailman/listinfo/jdev</a> Unsubscribe: <a href="mailto:JDev-unsubscribe@jabber.org" target="_blank" rel="noreferrer">JDev-unsubscribe@jabber.org</a> _______________________________________________ </blockquote></div>