Skip to main content

How to use XMPP / Jabber with a custom domain name

In order to use the "Extensible Messaging and Presence Protocol" (XMPP, formerly known as "Jabber") with a custom domain name, the following requirements must be met:

  • The features described below are available in all our price plans except for the LIGHT plan.

  • Your external domain must be configured at mailbox.org to be usable for e-mail addresses. If this is the case, an appropriate e-mail address can be used for your XMPP account.
    Our XMPP server will update its configuration once per hour, so there may be a small delay in getting your e-mail address up and running with the service.

  • The two entries shown below this list must be set up in the Domain Name System (DNS) settings for your external domain. This must be done at the provider where you registered your domain. Please make sure to replace "example.com" with your own domain name in the Listing 1 below.

  • When everything has been set up, please raise a support ticket at https://support.mailbox.org/
    and we will enable your domain for use with XMPP. Please be aware that it can take up to 24 hours for the necessary changes to be disseminated throughout the worldwide DNS.

Listing 1: DNS entries for your Jabber domains

_xmpp-client._tcp.example.com. 3600 IN SRV 0 5 5222 xmpp.mailbox.org. _xmpp-server._tcp.example.com. 3600 IN SRV 0 5 5269 xmpp.mailbox.org.

Once everything works, you can now set up your XMPP client with the e-mail address as a username and use your mailbox.org password. The DNS record tells your XMPP client the server it should connect to, and the other XMPP servers where to send your XMPP messages to.

Catch-all addresses are not possible

For technical reasons it is unfortunately not possible to use a catch-all e-mail account configured for a custom domain for XMPP accounts.

Self-signed SSL certificates​

Communication to our XMPP server is only possible via connections that are encrypted with "Transport Layer Security" (SSL/TLS). SSL/TLS uses digital certificates for secure encryption. We do not provide implementation of self-signed certificates.