That's why I said it may or may not qualify. What matters is if they are enabled and properly configured by default. My point is not whether ejabberd supports the needed XEP's.
RETROSHARE YUBIKEY ARCHIVE
Running XEP-0313: Message Archive Management (MUC)… FAILED Running XEP-0384: OMEMO Encryption… PASSED Running XEP-0368: SRV records for XMPP over TLS… FAILED Running XEP-0065: SOCKS5 Bytestreams (Proxy)… PASSED Running XEP-0363: HTTP File Upload… FAILED Use compliance suite 'Conversations Compliance Suite' to test server.tld Running XEP-0357: Push Notifications… PASSEDĪdvanced Server Mobile Compliance Suite: PASSED
Running XEP-0352: Client State Indication… PASSED Use compliance suite 'Advanced Server Mobile Compliance Suite' to test server.tld Running XEP-0313: Message Archive Management… FAILEDĪdvanced Server IM Compliance Suite: FAILED Running XEP-0198: Stream Management… PASSED Running XEP-0045: Multi-User Chat… PASSED Running XEP-0191: Blocking Command… PASSED Running XEP-0280: Message Carbons… PASSED Use compliance suite 'Advanced Server IM Compliance Suite' to test server.tld Running XEP-0163: Personal Eventing Protocol… PASSEDĪdvanced Server Core Compliance Suite: PASSED Running XEP-0115: Entity Capabilities… PASSED Use compliance suite 'Advanced Server Core Compliance Suite' to test server.tld The default ejabberd configuration in Debian Testing fails:
0 kommentar(er)
